Triple
T27553839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 58 |
E695579
|
entity |
| Predicate | hasTwoLaneHighwaySection |
P136017
|
FINISHED |
| Object | in rural Central Coast area |
—
|
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: in rural Central Coast area | Statement: [California State Route 58, hasTwoLaneHighwaySection, in rural Central Coast area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwoLaneHighwaySection Context triple: [California State Route 58, hasTwoLaneHighwaySection, in rural Central Coast area]
-
A.
hasTwoLaneSegmentsIn
Indicates that an entity contains or is composed of exactly two distinct lane segments within a specified context or area.
-
B.
isTwoLaneRoad
chosen
Indicates that the road consists of exactly two traffic lanes, typically one for each direction of travel.
-
C.
isFourLaneHighway
Indicates that a road segment functions as a highway consisting of four traffic lanes.
-
D.
hasFourLaneSections
Indicates that a road or route includes sections where it consists of four traffic lanes.
-
E.
isDividedHighway
Indicates that a roadway consists of physically separated carriageways for opposing directions of traffic.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f8e4ab88190bfe86343b948a401 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:36 p.m.