Triple
T36943495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Zitácuaro |
E913839
|
entity |
| Predicate | sideInsurgent |
P186759
|
FINISHED |
| Object | Mexican independence movement |
—
|
NE NERFINISHED |
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: Mexican independence movement | Statement: [Battle of Zitácuaro, sideInsurgent, Mexican independence movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInsurgent Context triple: [Battle of Zitácuaro, sideInsurgent, Mexican independence movement]
-
A.
endedInsurgencyType
Indicates the specific manner or category of outcome by which an insurgency was brought to an end.
-
B.
insurgentSupporter
Indicates that one entity supports, assists, or aligns with an insurgent group or insurgent activities.
-
C.
insurgentCapital
Indicates a relationship where a location functions as the primary base, stronghold, or central hub of operations for an insurgent group.
-
D.
strengthInsurgents
Indicates the level or extent of power, capability, or resources possessed by insurgent forces in a given context.
-
E.
rebelInstitution
Indicates that an institution actively resists, opposes, or defies an established authority, system, or governing power.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.