Triple
T37807275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GANA (Ghana) |
E942537
|
entity |
| Predicate | multiPartyContext |
P78032
|
FINISHED |
| Object | Ghanaian multi-party system |
—
|
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: Ghanaian multi-party system | Statement: [GANA (Ghana), multiPartyContext, Ghanaian multi-party system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiPartyContext Context triple: [GANA (Ghana), multiPartyContext, Ghanaian multi-party system]
-
A.
multiPartySystem
chosen
Indicates a relationship in which more than two distinct parties or entities are jointly involved in a shared process, interaction, or system.
-
B.
multiPartyCompetition
Indicates a competitive relationship in which more than two parties simultaneously vie against one another within the same context or arena.
-
C.
crossParty
Indicates a relationship or action that involves or spans members of different political parties.
-
D.
cooperationContext
Indicates the situational or environmental conditions under which two or more entities are cooperating or collaborating.
-
E.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.