Triple

T31306858
Position Surface form Disambiguated ID Type / Status
Subject Maku fortress E798354 entity
Predicate governingDynastyAtTimeOfBabsImprisonment P201082 FINISHED
Object Qajar dynasty 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: Qajar dynasty | Statement: [Maku fortress, governingDynastyAtTimeOfBabsImprisonment, Qajar dynasty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governingDynastyAtTimeOfBabsImprisonment
Context triple: [Maku fortress, governingDynastyAtTimeOfBabsImprisonment, Qajar dynasty]
  • A. capturedDuringReignOf
    Indicates that one entity was captured while another entity was in power or ruling (i.e., during the time span of that entity’s reign).
  • B. dynastyServed
    Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
  • C. builtDuringReignOf
    Indicates that something was constructed while a particular ruler or authority was in power.
  • D. periodOfCaptivity
    Indicates a time span during which an entity is held in captivity or confinement.
  • E. dynasticHouseInvolved
    Indicates that a particular dynastic house (royal or noble lineage) is involved in, associated with, or plays a role in the referenced event, entity, or relationship.
  • 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_69f224e0bd4c8190aab9b29a73f7aa3c completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69ffc704e1e88190884928a6a5c55a87 completed May 9, 2026, 11:45 p.m.
PD Predicate disambiguation batch_69ffc6b483d881908ad872e25fa6abc5 completed May 9, 2026, 11:43 p.m.
PDg Predicate description generation batch_69ffc70423f08190bd7c0625b21147a4 completed May 9, 2026, 11:45 p.m.
Created at: April 29, 2026, 9:14 p.m.