Triple
T1361010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buk District |
E29097
|
entity |
| Predicate | isLocatedInCountryCapital |
P5025
|
FINISHED |
| Object | false |
—
|
LITERAL 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: false | Statement: [Buk District, isLocatedInCountryCapital, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInCountryCapital Context triple: [Buk District, isLocatedInCountryCapital, false]
-
A.
locatedInCountryCapitalSystem
Indicates that an entity is situated in the capital city of a specified country within a country–capital relationship system.
-
B.
locatedInCapital
chosen
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
-
C.
usedInCapitalCityOf
Indicates that something is utilized or applied within the capital city of a specified region or country.
-
D.
countryCapitalLocatedOn
Indicates that the capital city of a country is situated on or directly adjacent to a specified geographic feature (such as a river, coast, or lake).
-
E.
capitalOfCountryLocatedOn
Indicates that a city serves as the capital of a country that is geographically located on a specified landmass or region.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b156b081909c99ada70a969fc0 |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.