Triple
T18968813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eilat Mazar |
E464110
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Eilat |
—
|
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: Eilat | Statement: [Eilat Mazar, givenName, Eilat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eilat Context triple: [Eilat Mazar, givenName, Eilat]
-
A.
Eilat
chosen
Eilat is Israel’s southernmost city and a major Red Sea resort and port known for its beaches, coral reefs, and tourism.
-
B.
Netanya
Netanya is a coastal city in central Israel on the Mediterranean Sea, known for its beaches, tourism, and role as a regional economic center.
-
C.
Ashdod
Ashdod is a major coastal city in southern Israel that serves as an important cultural and religious hub, including for the Karaite Jewish community.
-
D.
Nahariya
Nahariya is a coastal city in northern Israel on the Mediterranean Sea, known as a resort town and gateway to nearby attractions such as Rosh HaNikra.
-
E.
Hadera
Hadera is a coastal city in northern Israel known for its power station, beaches, and location between Tel Aviv and Haifa.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d618e2ec8190848a41733e6db2f1 |
completed | April 20, 2026, 7:30 a.m. |
Created at: April 10, 2026, noon