Triple

T15969405
Position Surface form Disambiguated ID Type / Status
Subject Medeba E387279 entity
Predicate ancientNameForm P20952 FINISHED
Object Medeba E387279 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: Medeba | Statement: [Medeba, ancientNameForm, Medeba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Medeba
Context triple: [Medeba, ancientNameForm, Medeba]
  • A. Medeba chosen
    Medeba is an ancient city east of the Dead Sea, known from biblical accounts and later as a significant settlement in the region of Moab.
  • B. Aïn Beïda
    Aïn Beïda is a city in northeastern Algeria known as a regional commercial and administrative center with historical roots dating back to the Ottoman period.
  • C. Ghadamisi
    Ghadamisi is an alternative name for the Ghadamès Berber language spoken in and around the oasis town of Ghadamès in western Libya.
  • D. Berrechid
    Berrechid is a rapidly growing city in northwestern Morocco known as an important agricultural and industrial hub within the Casablanca-Settat region.
  • E. Souk El Berka
    Souk El Berka is a historic covered market in the medina of Tunis, traditionally known for its jewelry trade and distinctive architectural character.
  • 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_69d86da94ccc819083d187f5dc6a123e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1572847f08190830e30125e829766 completed April 16, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffe46d180c81909be66f628d1bdf72 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:54 a.m.