Triple
T534548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viceroyalty of Peru |
E12296
|
entity |
| Predicate | notableRebellion |
P4698
|
FINISHED |
| Object | Túpac Amaru II rebellion |
—
|
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: Túpac Amaru II rebellion | Statement: [Viceroyalty of Peru, notableRebellion, Túpac Amaru II rebellion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRebellion Context triple: [Viceroyalty of Peru, notableRebellion, Túpac Amaru II rebellion]
-
A.
notableSubconflict
Indicates that one conflict is a significant, distinguishable component or episode within a larger overarching conflict.
-
B.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
C.
notableForce
Indicates that an entity is recognized as a significant or influential force affecting another entity, system, or context.
-
D.
uprising
chosen
Indicates a collective act of resistance or rebellion by a group against an established authority or ruling power.
-
E.
notableCampaign
Indicates that an entity is prominently associated with a particular campaign, such as by leading, featuring in, or being a key focus of that campaign.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.