Triple
T22161667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Northern Railway |
E547684
|
entity |
| Predicate | hadStreetRunningSegments |
P81212
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sacramento Northern Railway, hadStreetRunningSegments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStreetRunningSegments Context triple: [Sacramento Northern Railway, hadStreetRunningSegments, yes]
-
A.
streetRunningSections
Indicates sections of a route or track that run along or directly on public streets.
-
B.
hasStreetRunningTracks
Indicates that a location or area includes street-level tracks used for running or jogging.
-
C.
highwaySegment
Indicates a road section that forms part of a larger highway route.
-
D.
isPartiallyStreetRunning
chosen
Indicates that a transportation route or service operates with only some segments running directly along or within public streets, sharing space with regular street traffic.
-
E.
isStreetCircuitSection
Indicates that a given track segment is part of a street circuit section, i.e., a portion of a racing course laid out on public roads.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a2d8064819094d27ef9f15c6a1f |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.