Triple
T28103571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tête-de-Boule |
E710301
|
entity |
| Predicate | usedForPeopleOfRegion |
P177120
|
FINISHED |
| Object | upper Saint-Maurice River region |
—
|
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: upper Saint-Maurice River region | Statement: [Tête-de-Boule, usedForPeopleOfRegion, upper Saint-Maurice River region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForPeopleOfRegion Context triple: [Tête-de-Boule, usedForPeopleOfRegion, upper Saint-Maurice River region]
-
A.
usedForCountry
Indicates that something is used for, or serves a purpose related to, a specific country.
-
B.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
C.
usedInCountryOrRegion
Indicates that something (such as an item, concept, or practice) is utilized or applied within a specified country or region.
-
D.
usesRegionType
Indicates that one entity operates within, is configured for, or otherwise makes use of a specified type of region.
-
E.
usedInCountry
Indicates that something is utilized, applied, or in operation within the specified country.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 27, 2026, 9:06 p.m.