Triple
T20108629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burin—Burgeo |
E490264
|
entity |
| Predicate | federalElectoralDistrictType |
P134104
|
FINISHED |
| Object | rural riding |
—
|
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: rural riding | Statement: [Burin—Burgeo, federalElectoralDistrictType, rural riding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalElectoralDistrictType Context triple: [Burin—Burgeo, federalElectoralDistrictType, rural riding]
-
A.
electoralDistrictType
Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
-
B.
federalDistrictType
chosen
Indicates the specific category or classification of a federal district within a governmental or administrative system.
-
C.
typeOfDistrict
Indicates the specific category or classification to which a given district belongs.
-
D.
federalElectoralDistrictStatus
Indicates the official status or condition of a federal electoral district, such as whether it is active, abolished, or otherwise designated.
-
E.
partOfElectoralDistrictType
Indicates that one entity is a component or subdivision of a specified type of electoral district.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666ddb09881909ad2aedd1e8a78da |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:28 p.m.