Triple
T11938367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 69 |
E284108
|
entity |
| Predicate | isTollFreeOnMostSegments |
P82212
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Interstate 69, isTollFreeOnMostSegments, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTollFreeOnMostSegments Context triple: [Interstate 69, isTollFreeOnMostSegments, true]
-
A.
tollFreeForMostSections
chosen
Indicates that the majority of sections within something (such as a route, service, or facility) can be used without paying a toll.
-
B.
hasTollFreeSection
Indicates that a route, road, or transportation facility includes at least one segment where no toll is charged for use.
-
C.
tollFreeBridgedWith
Indicates that a toll-free communication channel is connected or linked via a bridging mechanism to another network, system, or call path.
-
D.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
E.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903094218819092e11b273d87de65 |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.