Triple
T37828027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caltrans District 1 roadway network |
E943118
|
entity |
| Predicate | includesCorridorType |
P26881
|
FINISHED |
| Object | coastal corridor |
—
|
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: coastal corridor | Statement: [Caltrans District 1 roadway network, includesCorridorType, coastal corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCorridorType Context triple: [Caltrans District 1 roadway network, includesCorridorType, coastal corridor]
-
A.
corridorType
chosen
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
B.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
C.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
hasParallelCorridorRole
Indicates that one entity serves in a corridor-related role that is parallel or equivalent to the corridor role of another entity.
-
E.
isStopOnCorridor
Indicates that a location functions as a designated stop situated along a corridor 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.