Triple
T13834023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate Highways in Indiana |
E332476
|
entity |
| Predicate | hasBeltway |
P9042
|
FINISHED |
| Object | Interstate 465 |
—
|
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 465 | Statement: [Interstate Highways in Indiana, hasBeltway, Interstate 465]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeltway Context triple: [Interstate Highways in Indiana, hasBeltway, Interstate 465]
-
A.
hasPhysicalBelt
Indicates that one entity possesses or is equipped with a physical belt as an item or feature.
-
B.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
-
C.
beltwayAround
chosen
Indicates that one roadway or route functions as a beltway encircling or surrounding another specified area or location.
-
D.
usesBeltSystem
Indicates that a subject employs a structured belt-ranking system (e.g., colored belts) to denote levels of skill, progress, or status.
-
E.
beltwayName
Indicates that a beltway (ring road or orbital highway) has a specific name.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de029a34bc8190ae892ef7b09fc9e9 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.