Triple

T25093282
Position Surface form Disambiguated ID Type / Status
Subject Changez Chamchawala E628520 entity
Predicate relationshipWithSaladinChamcha P176253 FINISHED
Object estranged 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: estranged | Statement: [Changez Chamchawala, relationshipWithSaladinChamcha, estranged]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipWithSaladinChamcha
Context triple: [Changez Chamchawala, relationshipWithSaladinChamcha, estranged]
  • A. relationshipToSalim mawla Abi Hudhayfa
    Indicates that the person has the relationship of being the client/freedman (mawla) of Abu Hudhayfa in relation to Salim.
  • B. relationshipToAlauddinKhalji
    Indicates the nature of a person or entity’s relationship or connection to Alauddin Khalji.
  • C. MamlukCommander
    Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
  • D. associatedSultan
    Indicates that one entity is linked or connected to a particular sultan in some relevant context or relationship.
  • E. relationToKhalidIbnAlWalid
    Indicates a relationship or association that an entity has with Khalid ibn al-Walid.
  • 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_69e2ff2f58e881908340527bc5d34f07 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f6dfcafd0c81908d86662948c539d6 completed May 3, 2026, 5:40 a.m.
PD Predicate disambiguation batch_69f6de07836481908785cde9c511920b completed May 3, 2026, 5:32 a.m.
PDg Predicate description generation batch_69f6df418f488190a5e7ff41f32dceda completed May 3, 2026, 5:38 a.m.
Created at: April 18, 2026, 6:24 a.m.