Triple

T37688649
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Purandar (1665) E938441 entity
Predicate requiredSuzeraintyAcceptanceBy P202538 FINISHED
Object Shivaji NE NERFINISHED

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: Shivaji | Statement: [Treaty of Purandar (1665), requiredSuzeraintyAcceptanceBy, Shivaji]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiredSuzeraintyAcceptanceBy
Context triple: [Treaty of Purandar (1665), requiredSuzeraintyAcceptanceBy, Shivaji]
  • A. requiredRatificationOf
    Indicates that one entity’s decision, agreement, or action must be formally approved or confirmed by another specified entity in order to take effect.
  • B. mandatedAcceptanceOf
    Indicates that one entity is required, by rule or authority, to accept or approve something from another entity.
  • C. requiresSanctioningBody
    Indicates that an action, event, or decision must be approved or authorized by a designated sanctioning authority or governing body.
  • D. requiredTerritorialCessionBy
    Indicates that one party is obligated to transfer control or ownership of territory to another party.
  • E. hasSovereignAuthority
    Indicates that one entity holds ultimate governing or ruling power over another entity or domain.
  • 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_69f76ed881408190bc62a969530a4a53 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a008e29f76881908e656dbbd7fceea3 completed May 10, 2026, 1:54 p.m.
PD Predicate disambiguation batch_6a008dc01b308190bc26e69814692f82 completed May 10, 2026, 1:53 p.m.
PDg Predicate description generation batch_6a008e29394481909b8d124c8265141f completed May 10, 2026, 1:54 p.m.
Created at: May 3, 2026, 4:18 p.m.