Triple
T5171244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W&OD Railroad Regional Park |
E116682
|
entity |
| Predicate | formerUseOfCorridor |
P61930
|
FINISHED |
| Object | railroad |
—
|
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: railroad | Statement: [W&OD Railroad Regional Park, formerUseOfCorridor, railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerUseOfCorridor Context triple: [W&OD Railroad Regional Park, formerUseOfCorridor, railroad]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
corridorType
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
C.
corridorOrientation
Indicates the directional alignment or bearing of a corridor relative to a reference frame or coordinate system.
-
D.
corridorRole
Indicates a relationship where an entity functions as or is assigned the role of a corridor within a spatial or architectural context.
-
E.
numberOfCorridors
Indicates the total count of corridors associated with or contained within a given entity or structure.
- F. None of above. chosen
Provenance (4 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79508610819087abec175da8c847 |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:45 p.m.