Triple
T6913222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage Corridor |
E159985
|
entity |
| Predicate | railroadLineClass |
P14639
|
FINISHED |
| Object | suburban commuter line |
—
|
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: suburban commuter line | Statement: [Heritage Corridor, railroadLineClass, suburban commuter line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadLineClass Context triple: [Heritage Corridor, railroadLineClass, suburban commuter line]
-
A.
railroadClass
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
-
B.
railwayLineType
chosen
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
C.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
D.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
E.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9dbca6c819091d8b65e54ada5d9 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.