Triple
T26848763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pacific Donner Pass line |
E675995
|
entity |
| Predicate | gradeType |
P161967
|
FINISHED |
| Object | mountain grade |
—
|
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 grade | Statement: [Southern Pacific Donner Pass line, gradeType, mountain grade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradeType Context triple: [Southern Pacific Donner Pass line, gradeType, mountain grade]
-
A.
gradeCategory
Indicates the classification of a grade into a broader category or level (such as letter grade, performance band, or pass/fail group).
-
B.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
-
C.
gradeHierarchy
Indicates a hierarchical relationship between grades or levels, where one grade is ranked above or below another in an ordered structure.
-
D.
gradingTypes
Indicates the types or categories of grading or evaluation methods associated with an entity.
-
E.
gradeWithin
Indicates that one value’s grade or level falls within a specified range or interval relative to another.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 5:14 a.m.