Triple
T37092790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deschambault-Grondines |
E918470
|
entity |
| Predicate | provincialSubdivision |
P766
|
FINISHED |
| Object | Quebec |
—
|
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: Quebec | Statement: [Deschambault-Grondines, provincialSubdivision, Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provincialSubdivision Context triple: [Deschambault-Grondines, provincialSubdivision, Quebec]
-
A.
provincialSubdivisionName
Indicates the name assigned to a first-level administrative or provincial subdivision within a larger territorial or political entity.
-
B.
realmSubdivision
Indicates a hierarchical relationship where one realm is a constituent subdivision or part of a larger realm.
-
C.
countrySubdivision
chosen
Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
-
D.
governingSubdivision
Indicates that one administrative or political unit serves as the governing authority over a smaller, subordinate territorial subdivision.
-
E.
citySubdivision
Indicates that one administrative or geographic unit is a smaller subdivision contained within a larger city.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:14 p.m.