Triple
T12615988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bithoor |
E301252
|
entity |
| Predicate | rebellionRole |
P88009
|
FINISHED |
| Object | base of operations for Nana Sahib in 1857 |
—
|
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: base of operations for Nana Sahib in 1857 | Statement: [Bithoor, rebellionRole, base of operations for Nana Sahib in 1857]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebellionRole Context triple: [Bithoor, rebellionRole, base of operations for Nana Sahib in 1857]
-
A.
roleInRevolt
chosen
Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
-
B.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
C.
roleInMutiny
Indicates that one entity participated in a mutiny with a specific role or capacity in that rebellious action.
-
D.
rebelInstitution
Indicates that an institution actively resists, opposes, or defies an established authority, system, or governing power.
-
E.
factionRole
Indicates the specific role, function, or position an entity holds within a particular faction or group.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.