Triple
T26409713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Benin government |
E663924
|
entity |
| Predicate | allowsMultiPartySystem |
P78032
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Republic of Benin government, allowsMultiPartySystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsMultiPartySystem Context triple: [Republic of Benin government, allowsMultiPartySystem, true]
-
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.
hasMultiPartySystemSince
Indicates that an entity has operated under a multi-party political system starting from a specified point in time.
-
C.
allowsOppositionParties
Indicates that an entity permits opposition political parties to exist, operate, and participate in the political process.
-
D.
hasNumberOfParties
Indicates the total count of distinct parties or participants involved in a given relationship, agreement, or event.
-
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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 26, 2026, 11:37 p.m.