Triple
T27389781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morris, Alabama |
E691489
|
entity |
| Predicate | isServedByInterstate |
P141439
|
FINISHED |
| Object | Interstate 65 |
—
|
NE NERFINISHED |
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: Interstate 65 | Statement: [Morris, Alabama, isServedByInterstate, Interstate 65]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isServedByInterstate Context triple: [Morris, Alabama, isServedByInterstate, Interstate 65]
-
A.
connectsToInterstate
Indicates that one roadway, route, or location has a direct connection or access point to an interstate highway.
-
B.
interstateHighwayPassesThrough
chosen
Indicates that a specific interstate highway physically traverses or runs through the geographic area or jurisdiction of a given place.
-
C.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
-
D.
isAuxiliaryInterstateOf
Indicates that one interstate highway functions as an auxiliary route (such as a spur, loop, or bypass) of another primary interstate highway.
-
E.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:25 p.m.