Triple
T22851161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Manipur |
E566357
|
entity |
| Predicate | resultOfAngloManipurWar |
P132344
|
FINISHED |
| Object | British paramountcy established |
—
|
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: British paramountcy established | Statement: [Kingdom of Manipur, resultOfAngloManipurWar, British paramountcy established]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfAngloManipurWar Context triple: [Kingdom of Manipur, resultOfAngloManipurWar, British paramountcy established]
-
A.
resultOfPequotWar
Indicates that the subject entity is an outcome, consequence, or product that occurred as a result of the Pequot War.
-
B.
sideInBattleOfBuxar
Indicates being a participating side or party in the Battle of Buxar.
-
C.
resultOfMilitaryCampaign
chosen
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
-
D.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb8b3588190b2bc8e7021f9ef10 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.