Triple
T396907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes–St. Lawrence system |
E9202
|
entity |
| Predicate | majorRiverMouth |
P3817
|
FINISHED |
| Object | St. Lawrence River mouth at Gulf of St. Lawrence |
—
|
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: St. Lawrence River mouth at Gulf of St. Lawrence | Statement: [Great Lakes–St. Lawrence system, majorRiverMouth, St. Lawrence River mouth at Gulf of St. Lawrence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRiverMouth Context triple: [Great Lakes–St. Lawrence system, majorRiverMouth, St. Lawrence River mouth at Gulf of St. Lawrence]
-
A.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
B.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
C.
mouthOfWatercourse
chosen
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
D.
cityAtMouth
Indicates that a city is located at or very near the mouth (outlet) of a river.
-
E.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.