Triple
T21452618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasauksing Swing Bridge |
E529252
|
entity |
| Predicate | primaryRailAccessFor |
P109925
|
FINISHED |
| Object | Parry Island |
—
|
NE NERFINISHED |
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: Parry Island | Statement: [Wasauksing Swing Bridge, primaryRailAccessFor, Parry Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailAccessFor Context triple: [Wasauksing Swing Bridge, primaryRailAccessFor, Parry Island]
-
A.
primaryRailLinkFor
chosen
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
B.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
-
C.
railwayAccess
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
-
D.
hasRailOrRoadAccess
Indicates that an entity is connected to or reachable by either a railway network, a road network, or both.
-
E.
primaryRailUse
Indicates the main or predominant purpose for which a rail line, segment, or facility is used (e.g., passenger, freight, or mixed traffic).
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d426d88190ae87ae9fac9c30a0 |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:07 p.m.