Triple
T32978352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alegría-Dulantzi |
E843728
|
entity |
| Predicate | belongsToProvinceCapital |
P174027
|
FINISHED |
| Object | Vitoria-Gasteiz |
—
|
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: Vitoria-Gasteiz | Statement: [Alegría-Dulantzi, belongsToProvinceCapital, Vitoria-Gasteiz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToProvinceCapital Context triple: [Alegría-Dulantzi, belongsToProvinceCapital, Vitoria-Gasteiz]
-
A.
isInProvinceWithCapital
chosen
Indicates that a place is located within a province whose administrative capital is a specified city.
-
B.
associatedWithProvinceCapital
Indicates that an entity has a relationship or connection to the capital city of a specific province.
-
C.
isProvincialCapital
Indicates that a location serves as the administrative capital of a province within a country or region.
-
D.
locatedInCountryCapitalOfProvince
Indicates that an entity is located in the country that contains the capital city of a specified province.
-
E.
adjacentToProvinceCapital
Indicates that a location is directly next to or bordering the capital city of a province.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:22 a.m.