Triple
T38128995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Djibloho Province |
E952163
|
entity |
| Predicate | countryCapitalPlannedIn |
P50962
|
FINISHED |
| Object | Ciudad de la Paz |
E56799
|
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: Ciudad de la Paz | Statement: [Djibloho Province, countryCapitalPlannedIn, Ciudad de la Paz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCapitalPlannedIn Context triple: [Djibloho Province, countryCapitalPlannedIn, Ciudad de la Paz]
-
A.
isPlannedRegionalCapitalOf
chosen
Indicates that a location has been officially designated to become the regional capital in the future, but is not yet serving as the current regional capital.
-
B.
countryCapitalOverlooked
Indicates that a country's capital city is being neglected, ignored, or insufficiently recognized in a given context or consideration.
-
C.
hostsCapitalOf
Indicates that one location serves as the capital city of another administrative or political entity.
-
D.
destinationCapitalOf
Indicates that a location serves as the capital city of the specified destination or region.
-
E.
countryCapitalOfLocatedCity
Indicates that a city serves as the capital of a country and is geographically located within that country.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417b23619c8190aab6c024dffaf336 |
completed | June 28, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.