Triple
T24906675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 Canadian federal election |
E623727
|
entity |
| Predicate | forParliament |
P81398
|
FINISHED |
| Object | 35th Canadian Parliament |
—
|
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: 35th Canadian Parliament | Statement: [1993 Canadian federal election, forParliament, 35th Canadian Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forParliament Context triple: [1993 Canadian federal election, forParliament, 35th Canadian Parliament]
-
A.
parliamentary
Indicates that an entity is related to, governed by, or characteristic of a parliamentary system, institution, or process.
-
B.
usesParliament
Indicates that one entity conducts its legislative or decision‑making processes through a parliamentary body or system.
-
C.
parliamentaryService
Indicates that an entity serves or has served as a member within a parliamentary body or legislature.
-
D.
parliamentaryInvolvement
Indicates involvement or participation of an entity in the activities, processes, or functions of a parliament or parliamentary body.
-
E.
parliamentEntry
chosen
Indicates that an entity assumes or is granted membership or a seat in a parliamentary body.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4236bc540819096275eb784a08719 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.