Triple
T3649630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tel Aviv District |
E77387
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Or Yehuda |
E281806
|
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: Or Yehuda | Statement: [Tel Aviv District, contains, Or Yehuda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Or Yehuda Context triple: [Tel Aviv District, contains, Or Yehuda]
-
A.
Or Yehuda
chosen
Or Yehuda is a city in central Israel, located in the Tel Aviv District and functioning largely as a residential suburb of the Tel Aviv metropolitan area.
-
B.
Yehuda
Yehuda is a Hebrew given name traditionally associated with the biblical tribe of Judah and commonly used in Jewish communities.
-
C.
Shlomo
Shlomo is the Hebrew name for King Solomon, the biblical monarch renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
-
D.
Shmuel
Shmuel is the Hebrew form of the biblical name Samuel, commonly used in Jewish religious and cultural contexts.
-
E.
Benzion
Benzion is a Hebrew masculine given name meaning "son of Zion," traditionally used in Jewish communities.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38fa1988190b630329700afc3dd |
completed | March 8, 2026, 6:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44f4002948190af41072962006f51 |
completed | March 13, 2026, 5:54 p.m. |
Created at: March 8, 2026, 3:24 p.m.