Triple
T21452617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasauksing Swing Bridge |
E529252
|
entity |
| Predicate | primaryRoadAccessFor |
P9041
|
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, primaryRoadAccessFor, Parry Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoadAccessFor Context triple: [Wasauksing Swing Bridge, primaryRoadAccessFor, Parry Island]
-
A.
isOnlyMajorRoadAccessTo
Indicates that one road is the sole major roadway providing access to a particular place or area.
-
B.
roadAccessVia
chosen
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
C.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
D.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
E.
roadAccessArea
Indicates that an area is designated for or provides access to a road, such as for entry, exit, or connection.
- 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.