Triple
T24445059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niles Canyon Railway |
E616378
|
entity |
| Predicate | trackLengthApprox |
P148011
|
FINISHED |
| Object | approximately 9 miles |
—
|
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: approximately 9 miles | Statement: [Niles Canyon Railway, trackLengthApprox, approximately 9 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackLengthApprox Context triple: [Niles Canyon Railway, trackLengthApprox, approximately 9 miles]
-
A.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
B.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
-
C.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
D.
trackLengthMiles
chosen
Indicates the length of a track measured in miles.
-
E.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29852c6908190ab5186cee3693625 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.