Triple
T9555905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South County Trailway |
E230538
|
entity |
| Predicate | railroadUseEnded |
P27833
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [South County Trailway, railroadUseEnded, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadUseEnded Context triple: [South County Trailway, railroadUseEnded, mid-20th century]
-
A.
railwayWorksClosed
Indicates that a railway workshop, depot, or related railway works facility has ceased operations or been officially closed.
-
B.
railServiceEnded
chosen
Indicates that a previously operating rail service has been discontinued or terminated.
-
C.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
D.
formerRailUse
Indicates that an entity previously served a particular railway-related function or purpose, but no longer does so.
-
E.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9927209c8190bbb494fc9003bc99 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.