Triple
T31867945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adirondack region of New York |
E813508
|
entity |
| Predicate | majorAccessHighway |
P385
|
FINISHED |
| Object | Interstate 87 |
—
|
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 87 | Statement: [Adirondack region of New York, majorAccessHighway, Interstate 87]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorAccessHighway Context triple: [Adirondack region of New York, majorAccessHighway, Interstate 87]
-
A.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
B.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
C.
isOnlyMajorRoadAccessTo
Indicates that one road is the sole major roadway providing access to a particular place or area.
-
D.
mainRoadInfrastructure
Indicates that a road segment functions as a primary or major route within the transportation infrastructure network.
-
E.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: April 30, 2026, 11:54 p.m.