Triple

T19735063
Position Surface form Disambiguated ID Type / Status
Subject Philistine army E473956 entity
Predicate associatedWith P37 FINISHED
Object Ashkelon NE NERFINISHED

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: Ashkelon | Statement: [Philistine army, associatedWith, Ashkelon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashkelon
Context triple: [Philistine army, associatedWith, Ashkelon]
  • A. Ashkelon chosen
    Ashkelon is an ancient coastal city in the southern Levant, historically significant as one of the principal cities of the Philistines.
  • B. Sha'ar Yafo
    Sha'ar Yafo is the Hebrew name for Jaffa Gate, one of the main historic entrances to Jerusalem’s Old City.
  • C. Ekron
    Ekron was an ancient Philistine city-state in the southern Levant, known as one of the five major cities of the Philistine pentapolis.
  • D. Hazor
    Hazor was an important ancient Canaanite city-state in northern Israel, known as one of the largest and most influential urban centers in the Levant during the Bronze and Iron Ages.
  • E. Kfar Hittim
    Kfar Hittim is a modern agricultural village in northern Israel, established near the historic site of Hittin close to the Sea of Galilee.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6515d138c8190a4c4d112ed5756a3 completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.