Triple
T30395264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New England–Quebec corridor |
E773198
|
entity |
| Predicate | keyHighway |
P385
|
FINISHED |
| Object | Interstate 89 |
—
|
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 89 | Statement: [New England–Quebec corridor, keyHighway, Interstate 89]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyHighway Context triple: [New England–Quebec corridor, keyHighway, Interstate 89]
-
A.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
B.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
C.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
expressway
Indicates that one location is connected to another by a high-speed, limited-access roadway designed for fast vehicular travel.
-
E.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685ac63248190a51b9e0e6ed89dab |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.