Triple
T10653482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umkhonto we Sizwe |
E251029
|
entity |
| Predicate | targetPolicy |
P860
|
FINISHED |
| Object | focus on symbolic and infrastructure targets |
—
|
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: focus on symbolic and infrastructure targets | Statement: [Umkhonto we Sizwe, targetPolicy, focus on symbolic and infrastructure targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPolicy Context triple: [Umkhonto we Sizwe, targetPolicy, focus on symbolic and infrastructure targets]
-
A.
targetedByPolicy
Indicates that an entity is the intended subject or focus of a specific policy’s rules, actions, or effects.
-
B.
trackingPolicy
Indicates a relationship where one party defines or applies rules governing how another party’s activities, data, or movements are monitored and recorded.
-
C.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
planningPolicy
Indicates that one entity establishes or defines rules, guidelines, or strategies governing how another entity should plan or make planning-related decisions.
-
E.
referencePolicy
Indicates that one entity defines rules or guidelines governing how another entity may be referred to, cited, or mentioned.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff85674819099bf40c9f4fede15 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.