Triple
T28022358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RENAMO |
E707722
|
entity |
| Predicate | transitionedToPoliticalParty |
P7695
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [RENAMO, transitionedToPoliticalParty, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionedToPoliticalParty Context triple: [RENAMO, transitionedToPoliticalParty, 1992]
-
A.
registeredAsPoliticalParty
chosen
Indicates that an entity is officially recorded and recognized as a political party by the relevant authority or registry.
-
B.
memberOfPoliticalMovement
Indicates that an entity belongs to, supports, or participates in a specific political movement.
-
C.
partyAffiliationStart
Indicates the point in time when an entity’s affiliation with a particular political party or organization begins.
-
D.
memberOfPoliticalInstitution
Indicates that an entity belongs to, serves in, or holds membership within a specific political body or institution.
-
E.
affectedPoliticalParty
Indicates that a political party is impacted or influenced by a particular event, action, policy, or situation.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 8:10 p.m.