Triple
T25866448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marmaraereğlisi |
E651629
|
entity |
| Predicate | directionFromIstanbul |
P166136
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [Marmaraereğlisi, directionFromIstanbul, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromIstanbul Context triple: [Marmaraereğlisi, directionFromIstanbul, west]
-
A.
isInDirectionFromBudapest
Indicates that one entity is located in a specified compass or geographic direction when measured outward starting from Budapest.
-
B.
distanceToIstanbulApproxKm
Indicates the approximate distance, measured in kilometers, between a given place and Istanbul.
-
C.
directionFromSarajevo
Indicates the cardinal or relative compass direction in which one entity is located when measured from Sarajevo as the point of reference.
-
D.
geographicalDirectionFromConstantinople
Indicates that one place is located in a specified cardinal or intercardinal direction relative to Constantinople.
-
E.
directionFromBucharest
Indicates the cardinal or relative direction in which one entity lies when measured from Bucharest.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 22, 2026, 8:07 a.m.