Triple
T32893412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 91 |
E841399
|
entity |
| Predicate | formerPassesThrough |
P151420
|
FINISHED |
| Object | California |
—
|
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: California | Statement: [U.S. Route 91, formerPassesThrough, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPassesThrough Context triple: [U.S. Route 91, formerPassesThrough, California]
-
A.
formerPassesThroughState
chosen
Indicates that an earlier or previous version of a route, path, or connection passed through a particular state.
-
B.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
controlsPassageThrough
Indicates having the authority or mechanism to regulate, permit, or restrict movement or access through a particular route, area, or gateway.
-
D.
passesThroughState
Indicates that something (such as a route, path, or process) traverses or goes through a particular state or region during its course.
-
E.
hasNavigationPass
Indicates that an entity possesses a valid authorization or pass granting it navigation or passage rights within a specified area or route.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: May 1, 2026, 1:18 a.m.