Triple
T29905801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa de San Felipe de Austria |
E759530
|
entity |
| Predicate | hasDepartmentCapitalSuccessor |
P31969
|
FINISHED |
| Object | Oruro |
—
|
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: Oruro | Statement: [Villa de San Felipe de Austria, hasDepartmentCapitalSuccessor, Oruro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartmentCapitalSuccessor Context triple: [Villa de San Felipe de Austria, hasDepartmentCapitalSuccessor, Oruro]
-
A.
hasDepartmentCapital
Indicates that a department has a specific city designated as its capital.
-
B.
hasCitySuccessor
Indicates that one city is the successor or replacement of another city, typically in terms of status, function, or administrative role.
-
C.
hasDepartmentCapitalNearby
Indicates that the subject entity has a departmental capital city located in close geographical proximity to it.
-
D.
successorStateCapital
chosen
Indicates that one state capital city has replaced another as the official capital of the same state or region.
-
E.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 29, 2026, 6:08 p.m.