Triple
T19937906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 18 |
E479222
|
entity |
| Predicate | mountainPassType |
P137910
|
FINISHED |
| Object | mountain highway |
—
|
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: mountain highway | Statement: [California State Route 18, mountainPassType, mountain highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainPassType Context triple: [California State Route 18, mountainPassType, mountain highway]
-
A.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
B.
controlledMountainPasses
Indicates that an entity had authority over and could regulate access through specific mountain passes.
-
C.
mountainRangeType
Indicates the classification or category of a mountain range based on its geological or geographical type.
-
D.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
E.
mountainSupported
Indicates that one entity provides physical or structural support to a mountain or mountainous formation.
- F. None of above. chosen
Provenance (4 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a190ac08190b9dc7955c9764a71 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.