Triple
T28300203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senators of the Conservative Party of Canada |
E713686
|
entity |
| Predicate | hasCaucus |
P185931
|
FINISHED |
| Object | Conservative Senate caucus |
—
|
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: Conservative Senate caucus | Statement: [Senators of the Conservative Party of Canada, hasCaucus, Conservative Senate caucus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaucus Context triple: [Senators of the Conservative Party of Canada, hasCaucus, Conservative Senate caucus]
-
A.
isCaucusOf
Indicates that one group functions as a caucus, or organized subgroup, within a larger organization, body, or assembly.
-
B.
hasCaucusType
Indicates that an entity is associated with a specific type or category of caucus.
-
C.
includesCaucuses
chosen
Indicates that one entity contains or encompasses caucus groups or caucus-related components within it.
-
D.
caucusesWith
Indicates that an individual or group aligns and regularly meets with a particular political caucus or faction to coordinate strategy and action.
-
E.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 27, 2026, 11:34 p.m.