Triple
T24727901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Credit Party of Canada |
E618204
|
entity |
| Predicate | hadParliamentaryCaucus |
P99884
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Social Credit Party of Canada, hadParliamentaryCaucus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadParliamentaryCaucus Context triple: [Social Credit Party of Canada, hadParliamentaryCaucus, yes]
-
A.
congressionalCaucusMembership
Indicates that an individual is a member of a specific congressional caucus or group within a legislative body.
-
B.
hadParliamentaryRepresentationIn
chosen
Indicates that an entity was represented by one or more members in a specified parliament or legislative body during a given time or period.
-
C.
hasMemberOfParliament
Indicates that an entity is represented by a specific individual serving as its Member of Parliament.
-
D.
ParliamentarianSide
Indicates that one entity is aligned with, represents, or belongs to the Parliamentarian side in a political or legislative context.
-
E.
servedInParliament
Indicates that a person has held a position as a member of a parliamentary body during some period of time.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:01 a.m.