Triple
T22103741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | June Rebellion of 1832 |
E546233
|
entity |
| Predicate | numberOfInsurgents |
P102794
|
FINISHED |
| Object | several thousand |
—
|
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: several thousand | Statement: [June Rebellion of 1832, numberOfInsurgents, several thousand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfInsurgents Context triple: [June Rebellion of 1832, numberOfInsurgents, several thousand]
-
A.
endedInsurgencyType
Indicates the specific manner or category of outcome by which an insurgency was brought to an end.
-
B.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
C.
insurgentCasualties
Indicates the number of insurgents who were killed, wounded, or otherwise rendered casualties in a given event or context.
-
D.
majorInsurgencySettlement
Indicates that a location is a primary site where an insurgency has been significantly active, organized, or based.
-
E.
hasNumberOfAssailants
chosen
Indicates the relationship specifying how many assailants are involved in a given event or situation.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129175a7881909549883f23c53dca |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.