Triple
T9591579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-229 |
E231430
|
entity |
| Predicate | isBypassRouteFor |
P83609
|
FINISHED |
| Object | Interstate 29 through St. Joseph |
—
|
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: Interstate 29 through St. Joseph | Statement: [I-229, isBypassRouteFor, Interstate 29 through St. Joseph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBypassRouteFor Context triple: [I-229, isBypassRouteFor, Interstate 29 through St. Joseph]
-
A.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
B.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
C.
isAccessRouteAround
chosen
Indicates that one entity serves as an access route that goes around or circumvents another entity.
-
D.
avoidsRoute
Indicates that an entity deliberately does not use or travel along a particular route.
-
E.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a10b85881908bfc783dcb7170aa |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.