Triple
T25975108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright, Kansas |
E645914
|
entity |
| Predicate | directionFromDodgeCity |
P167277
|
FINISHED |
| Object | east |
—
|
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: east | Statement: [Wright, Kansas, directionFromDodgeCity, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromDodgeCity Context triple: [Wright, Kansas, directionFromDodgeCity, east]
-
A.
isLocatedInDirectionFromKansasCity
Indicates that one place is situated in a specific cardinal or relative direction from Kansas City.
-
B.
directionFromFortWorth
Indicates the compass direction in which one entity is located relative to Fort Worth.
-
C.
directionRelativeToEmeraldCity
Indicates the compass direction or positional bearing of one place or object relative to the location of Emerald City.
-
D.
directionFromPhoenix
Indicates the cardinal or relative compass direction of an entity as measured from Phoenix.
-
E.
directionFromSaltLakeCity
Indicates the compass direction in which one entity is located relative to Salt Lake City.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 22, 2026, 8:51 a.m.