Triple
T12722632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uşak |
E304022
|
entity |
| Predicate | distanceToIstanbul |
P21189
|
FINISHED |
| Object | approximately 450 kilometres |
—
|
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 450 kilometres | Statement: [Uşak, distanceToIstanbul, approximately 450 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToIstanbul Context triple: [Uşak, distanceToIstanbul, approximately 450 kilometres]
-
A.
distanceToIstanbulApproxKm
chosen
Indicates the approximate distance, measured in kilometers, between a given place and Istanbul.
-
B.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
C.
distanceFromKayseri
Indicates the spatial distance between a given entity and the location of Kayseri.
-
D.
distanceToBerlin
Indicates the spatial distance between a given entity’s location and the city of Berlin.
-
E.
distanceToAmsterdam
Indicates the spatial distance between a given location and the city of Amsterdam.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:24 p.m.