Triple
T13579154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sincan |
E324364
|
entity |
| Predicate | isInNationalCapitalArea |
P66890
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sincan, isInNationalCapitalArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNationalCapitalArea Context triple: [Sincan, isInNationalCapitalArea, yes]
-
A.
locatedInNationCapitalRegion
chosen
Indicates that an entity is situated within the capital region of a specific nation.
-
B.
isPartOfFederalCity
Indicates that an entity is located within and administratively belongs to a designated federal city.
-
C.
isWithinFederalCapitalTerritory
Indicates that one entity is geographically located inside the boundaries of the federal capital territory of another governing body or jurisdiction.
-
D.
isNationalCentralCity
Indicates that a city holds the official status of a national-level central city within a country’s administrative or strategic planning system.
-
E.
isInStateCapitalRegionOf
Indicates that one entity is located within the capital region of the state to which the other entity belongs.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb03052088190a2b68c106059828e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.