Triple
T36548710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elostirion |
E901198
|
entity |
| Predicate | directionFromShire |
P196523
|
FINISHED |
| Object | far 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: far west | Statement: [Elostirion, directionFromShire, far west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromShire Context triple: [Elostirion, directionFromShire, far west]
-
A.
roadDirectionFromNorseman
Indicates the direction or path that a road takes when starting from Norseman.
-
B.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
C.
directionFromHamilton
Indicates the directional relationship of one location as measured outward starting from Hamilton.
-
D.
directionFromThirsk
Indicates the directional relationship of one place or object as measured outward starting from Thirsk as the reference point.
-
E.
geographicDirectionImpliedByName
Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.