Triple

T16948408
Position Surface form Disambiguated ID Type / Status
Subject Mizpah E411122 entity
Predicate roleAfterDestructionOfJerusalem P125344 FINISHED
Object administrative center under Babylonian rule 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: administrative center under Babylonian rule | Statement: [Mizpah, roleAfterDestructionOfJerusalem, administrative center under Babylonian rule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleAfterDestructionOfJerusalem
Context triple: [Mizpah, roleAfterDestructionOfJerusalem, administrative center under Babylonian rule]
  • A. statusAfterTempleDestruction
    Indicates the condition or state of an entity that applies specifically after the destruction of the temple.
  • B. secondTempleDestroyedBy
    Indicates that the Second Temple was destroyed by the specified agent or cause.
  • C. cededJerusalemBy
    Indicates a relationship where control or authority over Jerusalem is formally transferred or surrendered by one party to another.
  • D. lostJerusalemTo
    Indicates that one party surrendered control of Jerusalem to another, typically through defeat or loss in conflict.
  • E. firstTempleDestroyedBy
    Indicates that the specified agent or force is responsible for destroying the first temple associated with the given 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_69d886c886688190967be07322597ac9 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cfb4b1b08190b608d36a209ed6bd completed April 18, 2026, 6:38 p.m.
PD Predicate disambiguation batch_69e32b9aa8748190b248890aca86753d completed April 18, 2026, 6:58 a.m.
PDg Predicate description generation batch_69e355722040819098830dabf207ecd6 completed April 18, 2026, 9:57 a.m.
Created at: April 10, 2026, 5:31 a.m.