Triple
T1229067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STBP |
E26393
|
entity |
| Predicate | typeOfCoalition |
P17174
|
FINISHED |
| Object | multi-stakeholder coalition |
—
|
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: multi-stakeholder coalition | Statement: [STBP, typeOfCoalition, multi-stakeholder coalition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCoalition Context triple: [STBP, typeOfCoalition, multi-stakeholder coalition]
-
A.
coalitionType
chosen
Indicates the specific kind or category of coalition relationship that exists between the involved entities.
-
B.
formedByCoalition
Indicates that something (such as a group, government, or organization) came into existence through the alliance or joint effort of multiple distinct parties or factions.
-
C.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
D.
keyCoalition
Indicates a coalition relationship where an entity plays a central or decisive role within that coalition.
-
E.
governsInCoalition
Indicates that an entity exercises governing authority jointly with one or more partners as part of a political coalition.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be3dac2c8190914ff27173bb6b34 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.