Triple
T1288497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gwalior |
E27489
|
entity |
| Predicate | controlBeforeBattle |
P21850
|
FINISHED |
| Object | British control of Gwalior Fort |
—
|
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 control of Gwalior Fort | Statement: [Battle of Gwalior, controlBeforeBattle, British control of Gwalior Fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlBeforeBattle Context triple: [Battle of Gwalior, controlBeforeBattle, British control of Gwalior Fort]
-
A.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
B.
controlledBefore
chosen
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
-
C.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
D.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
E.
hasKeyBattle
Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d38d7c81908941edda9cac5d6a |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.