Triple

T26942255
Position Surface form Disambiguated ID Type / Status
Subject Mughal conquest of Sindh E678550 entity
Predicate secondaryBelligerent P180603 FINISHED
Object local Sindhi polities 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: local Sindhi polities | Statement: [Mughal conquest of Sindh, secondaryBelligerent, local Sindhi polities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryBelligerent
Context triple: [Mughal conquest of Sindh, secondaryBelligerent, local Sindhi polities]
  • A. coBelligerent
    Indicates that two or more parties are engaged in hostilities against a common enemy, typically as allies or coordinated participants in the same conflict.
  • B. majorBelligerent
    Indicates that an entity is a primary or principal participant in a conflict, war, or large-scale hostile engagement.
  • C. belligerentSupport
    Indicates support given to a party engaged in conflict or hostilities, often implying backing one side in a belligerent or warlike context.
  • D. conflictBelligerent
    Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
  • E. belligerentFor
    Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
  • 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_69eeeb4d69588190a7c912164a1c37b3 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f7465687bc8190a9da44d62b634ed7 completed May 3, 2026, 12:57 p.m.
PD Predicate disambiguation batch_69f743f4ceb08190a21fe7f4a99b166b completed May 3, 2026, 12:47 p.m.
PDg Predicate description generation batch_69f74654c09c819084879162eba9d641 completed May 3, 2026, 12:57 p.m.
Created at: April 27, 2026, 6:19 a.m.