Triple

T12788115
Position Surface form Disambiguated ID Type / Status
Subject Philistia E305684 entity
Predicate hasMajorCity P316 FINISHED
Object Ekron E482800 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: Ekron | Statement: [Philistia, hasMajorCity, Ekron]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ekron
Context triple: [Philistia, hasMajorCity, Ekron]
  • A. Ekron chosen
    Ekron was an ancient Philistine city-state in the southern Levant, known as one of the five major cities of the Philistine pentapolis.
  • B. Kiriath Baal
    Kiriath Baal is an ancient town mentioned in the Hebrew Bible, associated with the region of Judah and known as a site linked to the Ark of the Covenant.
  • C. Ashkelon
    Ashkelon is an ancient coastal city in the southern Levant, historically significant as one of the principal cities of the Philistines.
  • D. Kedesh
    Kedesh was an ancient city in the territory of the Israelite tribe of Naphtali, known as a Levitical city of refuge in the Hebrew Bible.
  • E. Sha'ar Yafo
    Sha'ar Yafo is the Hebrew name for Jaffa Gate, one of the main historic entrances to Jerusalem’s Old City.
  • 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_69d7bdf366888190a8cccb982606889c completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e5dbdb88190a1b06721ada51627 completed April 10, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f68ebeab2081908a6e38351613e3ed completed May 2, 2026, 11:54 p.m.
Created at: April 9, 2026, 5:30 p.m.