Triple
T37030463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zara |
E916475
|
entity |
| Predicate | locatedInPartOfRegion |
P96807
|
FINISHED |
| Object | eastern Central Anatolia |
—
|
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: eastern Central Anatolia | Statement: [Zara, locatedInPartOfRegion, eastern Central Anatolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPartOfRegion Context triple: [Zara, locatedInPartOfRegion, eastern Central Anatolia]
-
A.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
locatedInMetaregion
Indicates that one entity is geographically or administratively situated within a larger metaregion.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.