Triple
T31066722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 95 Exit 11 |
E791694
|
entity |
| Predicate | onDirection |
P117356
|
FINISHED |
| Object | northbound |
—
|
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: northbound | Statement: [Interstate 95 Exit 11, onDirection, northbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onDirection Context triple: [Interstate 95 Exit 11, onDirection, northbound]
-
A.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
B.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
C.
isDirection
chosen
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6957c0ca08190b0d521a93f81021a |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:01 p.m.