Triple
T34454098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Palace of Uvea |
E884454
|
entity |
| Predicate | locatedInDependencyOf |
P40
|
FINISHED |
| Object | French Republic |
E39253
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: French Republic | Statement: [Royal Palace of Uvea, locatedInDependencyOf, French Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDependencyOf Context triple: [Royal Palace of Uvea, locatedInDependencyOf, French Republic]
-
A.
usedInDependency
Indicates that one element is utilized as a dependency by another element, such that the latter relies on the former for its functionality or composition.
-
B.
derivativeLocatedIn
Indicates that something derived from or produced by an entity is located within or associated with a particular place or larger entity.
-
C.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
E.
isLocatedInReporter
Indicates that the reporter entity is situated within or associated with a specific location or context.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37181c9ff081909bb83283a55f5905 |
completed | June 20, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.