Triple
T2061790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish flag |
E45805
|
entity |
| Predicate | capitalCityUsage |
P20460
|
FINISHED |
| Object | widely displayed in Ankara |
—
|
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: widely displayed in Ankara | Statement: [Turkish flag, capitalCityUsage, widely displayed in Ankara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityUsage Context triple: [Turkish flag, capitalCityUsage, widely displayed in Ankara]
-
A.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
B.
countryCapitalRole
Indicates that one entity serves as the capital city of a given country, representing its primary administrative or governmental center.
-
C.
capitalCityOfCountry
Indicates that a city serves as the official capital of a specified country.
-
D.
usedInCapitalCityOf
chosen
Indicates that something is utilized or applied within the capital city of a specified region or country.
-
E.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d0ecf08190aec20338a6ba9911 |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.