Triple
T3707875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communist Party of Peru – Shining Path |
E80935
|
entity |
| Predicate | leaderCapturedBy |
P4712
|
FINISHED |
| Object | Peruvian security forces |
—
|
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: Peruvian security forces | Statement: [Communist Party of Peru – Shining Path, leaderCapturedBy, Peruvian security forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderCapturedBy Context triple: [Communist Party of Peru – Shining Path, leaderCapturedBy, Peruvian security forces]
-
A.
leaderCapturedAndExecuted
Indicates that a leader was seized by an opposing force and subsequently put to death as a consequence of that capture.
-
B.
capturedCommander
Indicates that one party has taken a military commander from another party into custody or control.
-
C.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
D.
capturedOff
Indicates that one entity has taken another entity away or into custody, removing it from its original location or control.
-
E.
capturedBy
chosen
Indicates that one entity has been seized, taken into control, or otherwise apprehended 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc580b08481908391283778d5ce14 |
completed | March 8, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.