Triple
T890464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunwar Singh |
E19225
|
entity |
| Predicate | roleIn1857Uprising |
P4056
|
FINISHED |
| Object | organized and led rebel forces in Bihar |
—
|
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: organized and led rebel forces in Bihar | Statement: [Kunwar Singh, roleIn1857Uprising, organized and led rebel forces in Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleIn1857Uprising Context triple: [Kunwar Singh, roleIn1857Uprising, organized and led rebel forces in Bihar]
-
A.
roleInColonies
Indicates the specific function, position, or responsibility an entity holds within one or more colonies.
-
B.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
C.
involvedIndependenceMovement
chosen
Indicates that an entity actively participated in or contributed to an independence movement seeking political or national self-determination.
-
D.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
roleInSpanishCivilWar
Indicates the specific involvement or function an entity had in the context of the Spanish Civil War.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad0086a081908c47c285896a1f3c |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.