Triple
T26043076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 2 |
E647748
|
entity |
| Predicate | mountainSegmentType |
P159897
|
FINISHED |
| Object | two-lane 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: two-lane highway | Statement: [California State Route 2, mountainSegmentType, two-lane highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainSegmentType Context triple: [California State Route 2, mountainSegmentType, two-lane highway]
-
A.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
B.
mountainPassType
Indicates the specific classification or category of a mountain pass based on its characteristics or use.
-
C.
mountainRangeType
Indicates the classification or category of a mountain range based on its geological or geographical type.
-
D.
hillType
Indicates the specific classification or category of a hill based on its form, characteristics, or context.
-
E.
hasMountainClassification
Indicates a classification relationship where a mountain is assigned a specific type, category, or classification.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606588684819087b366450d7c4fa9 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 9:08 a.m.