Triple
T31331576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manouane River |
E799044
|
entity |
| Predicate | toponymyAuthority |
P171250
|
FINISHED |
| Object | Commission de toponymie du Québec |
—
|
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: Commission de toponymie du Québec | Statement: [Manouane River, toponymyAuthority, Commission de toponymie du Québec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymyAuthority Context triple: [Manouane River, toponymyAuthority, Commission de toponymie du Québec]
-
A.
toponymSourceFor
Indicates that one entity serves as the origin, basis, or source from which another entity’s place name (toponym) is derived.
-
B.
toponymStatus
Indicates the status or classification of a place name within a geographic naming or toponymic system.
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
-
E.
toponymicFunction
Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f11ba548190b8ad25fafb07b62b |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:16 p.m.