Triple
T2032208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cajon Pass |
E44541
|
entity |
| Predicate | railroadFeature |
P16835
|
FINISHED |
| Object | multiple mainline tracks |
—
|
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: multiple mainline tracks | Statement: [Cajon Pass, railroadFeature, multiple mainline tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadFeature Context triple: [Cajon Pass, railroadFeature, multiple mainline tracks]
-
A.
railroadEngineeringFeature
Indicates a feature, element, or characteristic specifically related to the design, construction, or operation of railroad engineering systems.
-
B.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
C.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
-
D.
railTracks
chosen
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
E.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9313134819088133fb69b8f606f |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.