Triple
T10119046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canningite ministry |
E223236
|
entity |
| Predicate | coalitionContains |
P68851
|
FINISHED |
| Object | moderate Tories |
—
|
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: moderate Tories | Statement: [Canningite ministry, coalitionContains, moderate Tories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionContains Context triple: [Canningite ministry, coalitionContains, moderate Tories]
-
A.
hasCoalition
chosen
Indicates that an entity participates in, belongs to, or is associated with a coalition formed with one or more other entities.
-
B.
coalitionSupportedBy
Indicates that a coalition receives backing, endorsement, or assistance from a specified supporting entity.
-
C.
coalitionPotential
Indicates the potential or likelihood that two or more entities can form a cooperative alliance or coalition.
-
D.
coalitionPresence
Indicates the existence or involvement of a coalition within a given context, such as its presence in a location, event, or interaction.
-
E.
formedCoalitionWith
Indicates that two or more parties have joined together in a formal alliance or partnership to pursue shared goals or interests.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd26460a4819093a3b239d97c3e3d |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.