Triple
T37030471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zara |
E916475
|
entity |
| Predicate | locatedInGeographicalSubregion |
P118149
|
FINISHED |
| Object | Central Anatolia Region |
E80639
|
NE 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: Central Anatolia Region | Statement: [Zara, locatedInGeographicalSubregion, Central Anatolia Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGeographicalSubregion Context triple: [Zara, locatedInGeographicalSubregion, Central Anatolia Region]
-
A.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
B.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
C.
inCountrySubregion
chosen
Indicates that one location or entity is situated within a specific subregion of a country.
-
D.
originSubregion
Indicates the specific subregional area from which an entity originates or is derived.
-
E.
subregionName
Indicates that one region is identified by a specific name used for a smaller or subordinate geographic or administrative area within a larger region.
- F. None of above.
Provenance (4 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdb1f3d08190a293494eafc4c361 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.