Triple
T22407404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South West geopolitical zone |
E553911
|
entity |
| Predicate | federalCapitalWithinZone |
P117001
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [South West geopolitical zone, federalCapitalWithinZone, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalCapitalWithinZone Context triple: [South West geopolitical zone, federalCapitalWithinZone, none]
-
A.
isWithinFederalCapitalTerritory
Indicates that one entity is geographically located inside the boundaries of the federal capital territory of another governing body or jurisdiction.
-
B.
hasFederalCapitalWithin
Indicates that a country or federal entity has its official federal capital city located within the boundaries of a specified geographic area.
-
C.
isPartOfFederalCity
Indicates that an entity is located within and administratively belongs to a designated federal city.
-
D.
containsFederalCapitalTerritory
Indicates that a geopolitical entity includes within its boundaries a designated federal capital territory.
-
E.
capitalCityLocatedInZone
chosen
Indicates that a capital city is geographically situated within a specified zone or area.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158ba1c6481908e4b9b3635ed3a49 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.