Triple
T35050984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elsweyr |
E1011328
|
entity |
| Predicate | locatedInDirectionOnTamriel |
P201641
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Elsweyr, locatedInDirectionOnTamriel, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionOnTamriel Context triple: [Elsweyr, locatedInDirectionOnTamriel, south]
-
A.
regionDirection
chosen
Indicates a spatial relationship where one region is located in a specific directional orientation (e.g., north, south, above) relative to another region.
-
B.
directionFromShire
Indicates the relative compass direction of one place or object as measured outward from the Shire.
-
C.
directionFromCitadel
Indicates the spatial direction or orientation of one entity as measured outward from a citadel.
-
D.
hasDirectionWithinDoriath
Indicates that one entity has a directional orientation or path that lies within the boundaries of Doriath.
-
E.
geographicDirectionInColony
Indicates the relative geographic direction of one location or feature within the boundaries of a colony with respect to another reference point in that colony.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.