Triple
T10347273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trenton |
E243781
|
entity |
| Predicate | waterwayTerminusType |
P88669
|
FINISHED |
| Object | eastern terminus of the Trent–Severn Waterway |
—
|
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: eastern terminus of the Trent–Severn Waterway | Statement: [Trenton, waterwayTerminusType, eastern terminus of the Trent–Severn Waterway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayTerminusType Context triple: [Trenton, waterwayTerminusType, eastern terminus of the Trent–Severn Waterway]
-
A.
waterwayDestination
chosen
Indicates that a waterway leads to, flows into, or terminates at a specified destination.
-
B.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
C.
riverMouthType
Indicates the type or form of the feature where a river meets a larger body of water.
-
D.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
isTidalMouthOf
Indicates that one location is the tidal mouth or estuarine outlet through which a river or watercourse enters a larger body of water.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9251654819080d1e3f0ed4ee9d3 |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:56 a.m.