Triple
T18392003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Çumra |
E449752
|
entity |
| Predicate | distanceToÇatalhöyük |
P130949
|
FINISHED |
| Object | approximately 10–15 km |
—
|
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: approximately 10–15 km | Statement: [Çumra, distanceToÇatalhöyük, approximately 10–15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToÇatalhöyük Context triple: [Çumra, distanceToÇatalhöyük, approximately 10–15 km]
-
A.
distanceToAtapuerca
Indicates the spatial distance between a given entity and the location of Atapuerca.
-
B.
distanceToStonehenge
Indicates the measured or calculated spatial distance between a given entity and the location of Stonehenge.
-
C.
distanceToHampi
Indicates the measured or specified distance between a given entity or location and Hampi.
-
D.
distanceFromHadriansWall
Indicates the measured spatial distance between a given entity and Hadrian’s Wall.
-
E.
distanceFromAntalya
Indicates the spatial distance between a given place or object and the city of Antalya.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518435cf481908393c1eb2b4ba659 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:46 a.m.