Triple
T5022314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poughkeepsie Railroad Bridge |
E112880
|
entity |
| Predicate | reopenedAsWalkway |
P27832
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Poughkeepsie Railroad Bridge, reopenedAsWalkway, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsWalkway Context triple: [Poughkeepsie Railroad Bridge, reopenedAsWalkway, 2009]
-
A.
openedAsPedestrianBridge
chosen
Indicates that a structure began operation specifically for use as a pedestrian bridge.
-
B.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
C.
demolishedToMakeWayFor
Indicates that one entity was intentionally destroyed or removed in order to create space for another entity or development.
-
D.
rebuiltAsLiftBridge
Indicates that an existing structure was reconstructed or converted into a lift bridge.
-
E.
reopenedInNewBuilding
Indicates that an entity, after being closed or relocated, has resumed operations in a different, newly constructed building.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73656edc8190b802ad38d9552b58 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.