Triple
T34281714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-196 |
E879606
|
entity |
| Predicate | signedDirection |
P129985
|
FINISHED |
| Object | eastbound |
—
|
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: eastbound | Statement: [I-196, signedDirection, eastbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedDirection Context triple: [I-196, signedDirection, eastbound]
-
A.
isDirection
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
-
B.
notationDirection
Indicates the direction in which a notation-related element (such as a symbol, mark, or annotation) is oriented or applied relative to another element.
-
C.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
D.
definesDirection
Indicates that one entity specifies or establishes the orientation, course, or path along which another entity is directed or proceeds.
-
E.
directionType
chosen
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.