Triple

T27169389
Position Surface form Disambiguated ID Type / Status
Subject Takelot III E682862 entity
Predicate conflictsContext P3680 FINISHED
Object rival dynasties in Lower Egypt 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: rival dynasties in Lower Egypt | Statement: [Takelot III, conflictsContext, rival dynasties in Lower Egypt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conflictsContext
Context triple: [Takelot III, conflictsContext, rival dynasties in Lower Egypt]
  • A. conflictContext chosen
    Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
  • B. postConflictContext
    Indicates that the relationship or action occurs within, or is shaped by, a setting that follows the end of an armed conflict or violent confrontation.
  • C. conflictedBetween
    Indicates being torn or uncertain between two or more options, positions, or commitments.
  • D. conflictSideContext
    Indicates that an entity participates in a conflict on a particular side, within a specified contextual framing (such as time, place, or specific phase of the conflict).
  • E. conflictsOccurIn
    Indicates that one or more conflicts take place within, or are situated in, a specified context, location, or setting.
  • 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_69eefacf6e788190a75a64399d9e3109 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a931748190a637e631a52bbfaa completed May 2, 2026, 7:34 p.m.
Created at: April 27, 2026, 9:22 a.m.