Triple
T22686955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicolet, Quebec |
E560941
|
entity |
| Predicate | locatedInPartOfQuebec |
P149249
|
FINISHED |
| Object | south shore of the St. Lawrence River |
—
|
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: south shore of the St. Lawrence River | Statement: [Nicolet, Quebec, locatedInPartOfQuebec, south shore of the St. Lawrence River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPartOfQuebec Context triple: [Nicolet, Quebec, locatedInPartOfQuebec, south shore of the St. Lawrence River]
-
A.
locatedInAtlanticCanada
Indicates that the subject is geographically situated within the Atlantic Canada region.
-
B.
usedInCanadianProvince
Indicates that something is utilized, applied, or in operation within the jurisdiction of a Canadian province.
-
C.
regionCanada
Indicates that an entity is located in, associated with, or pertains to the geographic region of Canada.
-
D.
integratedIntoQuebecCity
Indicates that one entity has been incorporated or merged into the administrative or territorial structure of Quebec City.
-
E.
mouthProvince
Indicates that a river or watercourse has its mouth located within a particular province.
- F. None of above. chosen
Provenance (4 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178649aac8190a9d41f5d82895bdf |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:13 p.m.