Triple
T5328524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | leadership of the Liberal Party of Canada |
E123245
|
entity |
| Predicate | canBeVacantDueTo |
P35080
|
FINISHED |
| Object | resignation |
—
|
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: resignation | Statement: [leadership of the Liberal Party of Canada, canBeVacantDueTo, resignation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeVacantDueTo Context triple: [leadership of the Liberal Party of Canada, canBeVacantDueTo, resignation]
-
A.
canBeVacantWhen
chosen
Indicates the conditions or circumstances under which something is allowed or able to remain unoccupied or empty.
-
B.
canBeVacated
Indicates that a position, status, or decision is capable of being annulled, set aside, or rendered void.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
E.
canBeDisabledOn
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced entity.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8593bd6c8190b2054e548ddf2458 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.