Triple
T18429476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalıhüyük |
E450225
|
entity |
| Predicate | isInCentralTurkey |
P131567
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yalıhüyük, isInCentralTurkey, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCentralTurkey Context triple: [Yalıhüyük, isInCentralTurkey, true]
-
A.
statusInTurkey
Indicates the legal, social, or official condition or standing that an entity holds within the context of Turkey.
-
B.
wasOttomanCity
Indicates that a location previously functioned as a city within the territorial or administrative domain of the Ottoman Empire.
-
C.
notUnderFullOttomanControl
Indicates that the entity or region was not completely governed, administered, or dominated by the Ottoman Empire.
-
D.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
E.
locatedInCentralEurope
Indicates that something is geographically situated within the region of Central Europe.
- F. None of above. chosen
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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b15e2e081908c96c5678ff4b941 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:26 a.m.