Triple
T7790480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-285 and I-20 east interchange |
E187363
|
entity |
| Predicate | accessesDirection |
P42312
|
FINISHED |
| Object | I-20 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: I-20 eastbound | Statement: [I-285 and I-20 east interchange, accessesDirection, I-20 eastbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesDirection Context triple: [I-285 and I-20 east interchange, accessesDirection, I-20 eastbound]
-
A.
accessDirection
chosen
Indicates the direction or orientation from which access to something is obtained or permitted.
-
B.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
C.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7ea13f08190a60c5f1863bce816 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa48a166c8190a5da0046bde4d9ee |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:25 p.m.