Triple
T3703837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saskatoon |
E80843
|
entity |
| Predicate | numberOfRiverBridges |
P20771
|
FINISHED |
| Object | multiple road and rail bridges |
—
|
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: multiple road and rail bridges | Statement: [Saskatoon, numberOfRiverBridges, multiple road and rail bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRiverBridges Context triple: [Saskatoon, numberOfRiverBridges, multiple road and rail bridges]
-
A.
hasNumberOfBridges
chosen
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
B.
bridgeSpans
Indicates that a bridge extends across and connects two separate points or areas.
-
C.
bridges
Indicates that one entity connects or links two or more other entities, allowing passage, transition, or interaction between them.
-
D.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
E.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54aaac88190b775dba2513b6d4a |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84eeca48190bb4de637e9f0e27a |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:33 p.m.