Triple
T27696450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ville de Baie-Comeau |
E698306
|
entity |
| Predicate | isOnMajorWaterway |
P58979
|
FINISHED |
| Object | Saint Lawrence River |
—
|
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: Saint Lawrence River | Statement: [Ville de Baie-Comeau, isOnMajorWaterway, Saint Lawrence River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnMajorWaterway Context triple: [Ville de Baie-Comeau, isOnMajorWaterway, Saint Lawrence River]
-
A.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
B.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
C.
isOnWatercourse
chosen
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
D.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359fecc081908e1794c1905c5cc4 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:54 p.m.