Triple
T23539706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 46th Canadian federal election |
E577704
|
entity |
| Predicate | willUse |
P150157
|
FINISHED |
| Object | single-member electoral districts |
—
|
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: single-member electoral districts | Statement: [46th Canadian federal election, willUse, single-member electoral districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willUse Context triple: [46th Canadian federal election, willUse, single-member electoral districts]
-
A.
exportUse
Indicates that something is used, intended, or suitable for export from one place or market to another.
-
B.
likelyUse
chosen
Indicates that one entity is expected or probable to use, employ, or make use of another entity in a given context.
-
C.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
E.
deltaUse
Indicates a change in how something is used or the difference between two states of usage.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1a66b88190811b38523ea606fe |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.