Triple
T7544377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 36 |
E178360
|
entity |
| Predicate | roadCharacteristic |
P1777
|
FINISHED |
| Object | winding |
—
|
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: winding | Statement: [California State Route 36, roadCharacteristic, winding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadCharacteristic Context triple: [California State Route 36, roadCharacteristic, winding]
-
A.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
B.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
roadEnvironment
Indicates that the relationship or action occurs within, is influenced by, or is specifically associated with a road or roadway environment.
-
D.
isCarriagewayOf
Indicates that a given road segment functions as a carriageway that forms part of, or belongs to, a larger road or route.
-
E.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f896a27481908b2e120208f268e7 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.