Triple
T14760817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas County |
E346854
|
entity |
| Predicate | isLocatedInDirectionOf |
P29992
|
FINISHED |
| Object | northwestern Oklahoma |
—
|
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: northwestern Oklahoma | Statement: [Texas County, isLocatedInDirectionOf, northwestern Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInDirectionOf Context triple: [Texas County, isLocatedInDirectionOf, northwestern Oklahoma]
-
A.
isInDirectionOf
chosen
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
B.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
C.
directionRelativeTo
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
-
D.
isInTravelDirection
Indicates that one entity lies along or matches the direction in which another entity is traveling or moving.
-
E.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f207dc819088a53f717736a121 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.