Triple
T5608765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts rail trail network |
E147299
|
entity |
| Predicate | usesCorridorType |
P26881
|
FINISHED |
| Object | former railroad corridors |
—
|
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: former railroad corridors | Statement: [Massachusetts rail trail network, usesCorridorType, former railroad corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCorridorType Context triple: [Massachusetts rail trail network, usesCorridorType, former railroad corridors]
-
A.
corridorType
chosen
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
B.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
C.
corridorOrientation
Indicates the directional alignment or bearing of a corridor relative to a reference frame or coordinate system.
-
D.
formerUseOfCorridor
Indicates that a corridor was previously used for a particular purpose or function, but is no longer used in that way.
-
E.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fe7ee0819088ced51afd9a4f93 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.