Triple

T34125138
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 30 in Indiana E875254 entity
Predicate nearbyInterstateConnection P125461 FINISHED
Object Interstate 65 at Merrillville 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 at Merrillville | Statement: [U.S. Route 30 in Indiana, nearbyInterstateConnection, Interstate 65 at Merrillville]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearbyInterstateConnection
Context triple: [U.S. Route 30 in Indiana, nearbyInterstateConnection, Interstate 65 at Merrillville]
  • A. nearestInterstateHighway
    Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
  • B. nearestInterstateExit
    Indicates the relationship where a given location is associated with the closest interstate highway exit to it.
  • C. nearInterstate
    Indicates that one entity is located close to or in the immediate vicinity of an interstate highway.
  • D. motorwayJunctionNearby
    Indicates that a motorway junction is located close to the referenced entity.
  • E. connectsToInterstate chosen
    Indicates that one roadway, route, or location has a direct connection or access point to an interstate highway.
  • 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_69f349aa33848190a2e6c5e4533c8444 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fe629b4fa481908467c7c41b77f0c6 completed May 8, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69fe61bb260c819083f9378a3a06ca47 completed May 8, 2026, 10:20 p.m.
Created at: May 1, 2026, 1:53 a.m.