Triple
T33945588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brockville and Ottawa Railway |
E870280
|
entity |
| Predicate | riverTerminus |
P4359
|
FINISHED |
| Object | St. Lawrence River at Brockville |
—
|
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: St. Lawrence River at Brockville | Statement: [Brockville and Ottawa Railway, riverTerminus, St. Lawrence River at Brockville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverTerminus Context triple: [Brockville and Ottawa Railway, riverTerminus, St. Lawrence River at Brockville]
-
A.
waterwayDestination
Indicates that a waterway leads to, flows into, or terminates at a specified destination.
-
B.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
C.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
D.
mouthOfTheWatercourse
chosen
Indicates the location where a watercourse ends and flows into a larger body of water.
-
E.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:49 a.m.