Triple

T3175779
Position Surface form Disambiguated ID Type / Status
Subject Herodian dynasty E66461 entity
Predicate appliesToJurisdiction P82 FINISHED
Object Idumea E21554 NE 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: Idumea | Statement: [Herodian dynasty, appliesToJurisdiction, Idumea]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Idumea
Context triple: [Herodian dynasty, appliesToJurisdiction, Idumea]
  • A. Idumea chosen
    Idumea was an ancient region south of Judea, inhabited by the Edomites and later integrated into the Hasmonean and Herodian Jewish realms.
  • B. Iadera
    Iadera is the ancient Roman and medieval Latin name for the coastal city now known as Zadar in Croatia.
  • C. Uruca
    Uruca is a district of San José, Costa Rica, known as an important industrial and commercial area within the capital.
  • D. Duitama
    Duitama is a Colombian city in the Andean highlands known as an important commercial and transport hub within the Boyacá region.
  • E. Erba
    Erba is a town in the Lombardy region of northern Italy, situated near Lake Como and known for its scenic surroundings and local industry.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ad8586a34c8190944c63ec11a8de1a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada671e6848190a683eec1519b9268 completed March 8, 2026, 4:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69b235f16e60819091cbdb76130ecc40 completed March 12, 2026, 3:41 a.m.
Created at: March 8, 2026, 3:06 p.m.