Triple
T24084270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Party of Canada |
E596589
|
entity |
| Predicate | founderPositionAtFounding |
P105057
|
FINISHED |
| Object | Member of Parliament |
—
|
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: Member of Parliament | Statement: [People's Party of Canada, founderPositionAtFounding, Member of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderPositionAtFounding Context triple: [People's Party of Canada, founderPositionAtFounding, Member of Parliament]
-
A.
foundedByPosition
chosen
Indicates that an organization or entity was founded by a person serving in a specific role or position, rather than by a named individual alone.
-
B.
ownerAtFounding
Indicates that an entity is the owner of another entity at the time the latter is founded or established.
-
C.
founderBirthPlace
Indicates the place where the founder of an entity was born.
-
D.
goalAtFounding
Indicates that an entity had a particular goal or intended purpose at the time it was founded.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc279ac48190b60a0753981f0b97 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.