Triple
T71126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donner Pass |
E1422
|
entity |
| Predicate | isOnRoute |
P2127
|
FINISHED |
| Object | historic California Trail vicinity |
—
|
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: historic California Trail vicinity | Statement: [Donner Pass, isOnRoute, historic California Trail vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRoute Context triple: [Donner Pass, isOnRoute, historic California Trail vicinity]
-
A.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
B.
followsRouteOf
chosen
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
C.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
D.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
E.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f6997c081908b202f937eb2b14f |
completed | Feb. 28, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69a24eab7f408190a8275cb82474f575 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.