Triple
T34637451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee and Virginia |
E889466
|
entity |
| Predicate | shareFederalHighwaySystem |
P105705
|
FINISHED |
| Object | U.S. Interstate Highway System |
—
|
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: U.S. Interstate Highway System | Statement: [Tennessee and Virginia, shareFederalHighwaySystem, U.S. Interstate Highway System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareFederalHighwaySystem Context triple: [Tennessee and Virginia, shareFederalHighwaySystem, U.S. Interstate Highway System]
-
A.
highwayNumberingSystem
Indicates a system that assigns and organizes numerical designations to highways within a road network.
-
B.
nationalHighwayNetworkState
chosen
Indicates that a state is part of, or associated with, the national highway network.
-
C.
UShighwayNumber
Indicates that a U.S. highway is identified by a specific route number.
-
D.
primaryInterstateHighway
Indicates that the subject is designated as a primary (main) interstate highway within the interstate highway system.
-
E.
highwayNumberingScheme
Indicates the system or method by which highways are assigned their route numbers or designations.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: May 1, 2026, 2:04 a.m.