Triple

T7147356
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Allahabad E166601 entity
Predicate consequenceForMughalEmperor P812 FINISHED
Object loss of effective territorial control 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: loss of effective territorial control | Statement: [Treaty of Allahabad, consequenceForMughalEmperor, loss of effective territorial control]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceForMughalEmperor
Context triple: [Treaty of Allahabad, consequenceForMughalEmperor, loss of effective territorial control]
  • A. predecessorAsMughalEmperor
    Indicates that one entity served as the Mughal emperor immediately before another entity in the line of succession.
  • B. concludedUnderEmperor
    Indicates that an event, agreement, or process was completed or formally concluded during the reign of a specific emperor.
  • C. militaryConsequence
    Indicates a causal relationship where one event, action, or condition leads to a specific outcome or effect in the military domain (such as changes in capability, strategy, or conflict status).
  • D. hasConsequence chosen
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • E. emperorKilled
    Indicates that an emperor caused the death of 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_69c68886779c8190a8e3fbabffe68253 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e7d4f3388190941f03fd80b0c223 completed March 27, 2026, 8:25 p.m.
PD Predicate disambiguation batch_69c6e1c932888190b125ca3785b18553 completed March 27, 2026, 8 p.m.
Created at: March 27, 2026, 2:46 p.m.