Triple
T11790386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel Railways |
E280371
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Ashkelon |
E481064
|
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: Ashkelon | Statement: [Israel Railways, servesCity, Ashkelon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashkelon Context triple: [Israel Railways, servesCity, 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.
Tel Zayit
Tel Zayit is an archaeological mound in Israel’s Shephelah region, known for discoveries such as the Tel Zayit Abecedary that shed light on early Hebrew writing and Iron Age settlement.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417604a7c819097a601880b88ea6a |
completed | May 1, 2026, 3 a.m. |
Created at: April 8, 2026, 9:42 p.m.