Triple
T35123307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 70 in California |
E1014223
|
entity |
| Predicate | followedCorridorOf |
P113763
|
FINISHED |
| Object | Valley Boulevard |
—
|
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: Valley Boulevard | Statement: [U.S. Route 70 in California, followedCorridorOf, Valley Boulevard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedCorridorOf Context triple: [U.S. Route 70 in California, followedCorridorOf, Valley Boulevard]
-
A.
followedCorridor
chosen
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
-
B.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
C.
focusesOnCorridor
Indicates that an action, attention, or process is directed specifically toward a corridor or passageway.
-
D.
onCorridorTo
Indicates that one location is directly connected to another via a corridor leading toward it.
-
E.
locatedInTravelDirectionCorridor
Indicates that something is positioned within a corridor that lies along the direction of travel.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 3, 2026, 4:01 p.m.