Triple
T11327581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Mlangeni |
E268260
|
entity |
| Predicate | roleInUmkhontoWeSizwe |
P9463
|
FINISHED |
| Object | sabotage operations organizer |
—
|
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: sabotage operations organizer | Statement: [Andrew Mlangeni, roleInUmkhontoWeSizwe, sabotage operations organizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUmkhontoWeSizwe Context triple: [Andrew Mlangeni, roleInUmkhontoWeSizwe, sabotage operations organizer]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
C.
roleDuringBlackHawkWar
Indicates the specific role, position, or function an entity held during the Black Hawk War.
-
D.
roleInClub
Indicates that an entity holds a specific position or function within a particular club.
-
E.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.