Triple
T37757369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usui Pass |
E941152
|
entity |
| Predicate | railwayGradientType |
P121368
|
FINISHED |
| Object | rack-and-pinion section (historical) |
—
|
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: rack-and-pinion section (historical) | Statement: [Usui Pass, railwayGradientType, rack-and-pinion section (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayGradientType Context triple: [Usui Pass, railwayGradientType, rack-and-pinion section (historical)]
-
A.
railwayGradient
chosen
Indicates the slope or steepness of a railway track along its route.
-
B.
railroadGrade
Indicates that one entity is at the elevation or level of a railroad track or crossing relative to another entity.
-
C.
roadMaximumGradient
Indicates the steepest allowable slope or incline specified for a road segment.
-
D.
slopeType
Indicates the classification of a slope based on its geometric or physical characteristics, such as steepness, shape, or orientation.
-
E.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:19 p.m.