Triple
T28086379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental Region of Equatorial Guinea |
E709830
|
entity |
| Predicate | plannedCapitalRelocationTo |
P60806
|
FINISHED |
| Object | Ciudad de la Paz |
—
|
NE NERFINISHED |
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: Ciudad de la Paz | Statement: [Continental Region of Equatorial Guinea, plannedCapitalRelocationTo, Ciudad de la Paz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedCapitalRelocationTo Context triple: [Continental Region of Equatorial Guinea, plannedCapitalRelocationTo, Ciudad de la Paz]
-
A.
isPlannedToBeReplacedAsCapitalBy
chosen
Indicates that one capital city is intended or scheduled to be superseded by another as the official capital.
-
B.
hasRelocationPlan
Indicates that an entity has an established or intended plan to move from its current location to a different one.
-
C.
cityAfterRelocation
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
D.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
dateCapitalMoved
Indicates the date on which a capital city was officially relocated from one place to another.
- F. None of above.
Provenance (3 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 8:55 p.m.