Triple

T1288498
Position Surface form Disambiguated ID Type / Status
Subject Battle of Gwalior E27489 entity
Predicate controlDuringBattle P28108 FINISHED
Object temporary rebel 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: temporary rebel control of Gwalior Fort | Statement: [Battle of Gwalior, controlDuringBattle, temporary rebel control of Gwalior Fort]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controlDuringBattle
Context triple: [Battle of Gwalior, controlDuringBattle, temporary rebel 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. usedInBattle
    Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
  • C. garrisonDuringBattle
    Indicates that an entity is stationed to defend or hold a location specifically during the time a battle is taking place.
  • D. battleOccurred
    Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
  • E. battleDuration
    Indicates the length of time for which a particular battle or combat event lasts.
  • F. None of above. chosen

Provenance (4 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.
PDg Predicate description generation batch_69a4bfa205ec81909d8170b398345615 completed March 1, 2026, 10:37 p.m.
Created at: March 1, 2026, 7:51 p.m.