Triple
T28022356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RENAMO |
E707722
|
entity |
| Predicate | activeAsRebelMovementFrom |
P149848
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [RENAMO, activeAsRebelMovementFrom, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsRebelMovementFrom Context triple: [RENAMO, activeAsRebelMovementFrom, 1976]
-
A.
foundedAsRebelMovement
chosen
Indicates that an organization or group was originally established as a rebel or insurgent movement opposing an existing authority or regime.
-
B.
associatedWithRebelGroup
Indicates that one entity is connected or linked in some capacity to a rebel group, such as through membership, support, collaboration, or affiliation.
-
C.
rebelInstitution
Indicates that an institution actively resists, opposes, or defies an established authority, system, or governing power.
-
D.
earlierRebelGroup
Indicates that one rebel group existed or was active before another rebel group in time.
-
E.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
- 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_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 8:10 p.m.