Triple
T28022357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RENAMO |
E707722
|
entity |
| Predicate | activeAsRebelMovementUntil |
P171445
|
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, activeAsRebelMovementUntil, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsRebelMovementUntil Context triple: [RENAMO, activeAsRebelMovementUntil, 1992]
-
A.
foundedAsRebelMovement
Indicates that an organization or group was originally established as a rebel or insurgent movement opposing an existing authority or regime.
-
B.
rebellionOccurredAfter
Indicates that the rebellion took place later in time than the referenced event or situation.
-
C.
earlierRebelGroup
Indicates that one rebel group existed or was active before another rebel group in time.
-
D.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
E.
joinedRebellion
Indicates that an entity became a member or active participant in a rebellion against an established authority.
- F. None of above. chosen
Provenance (4 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_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 8:10 p.m.