Triple
T2786172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great American Rail-Trail |
E61815
|
entity |
| Predicate | usesCorridors |
P5520
|
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: [Great American Rail-Trail, usesCorridors, former railroad corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCorridors Context triple: [Great American Rail-Trail, usesCorridors, former railroad corridors]
-
A.
hasCorridor
chosen
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
numberOfCorridors
Indicates the total count of corridors associated with or contained within a given entity or structure.
-
C.
lengthOfCorridors
Indicates the measured extent or distance of corridors within a given space or structure.
-
D.
corridorType
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
E.
corridorOrientation
Indicates the directional alignment or bearing of a corridor relative to a reference frame or coordinate system.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.