Triple
T4079224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasmon |
E87436
|
entity |
| Predicate | nameInEnglish |
P3437
|
FINISHED |
| Object | Hasmon |
E87436
|
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: Hasmon | Statement: [Hasmon, nameInEnglish, Hasmon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hasmon Context triple: [Hasmon, nameInEnglish, Hasmon]
-
A.
Hasmon
chosen
Hasmon is the ancestral figure from whom the Hasmonean dynasty of Judea traditionally traces its name and lineage.
-
B.
Yehud-Monosson
Yehud-Monosson is a small Israeli city in central Israel, located near Tel Aviv and formed by the merger of the town of Yehud with the adjacent community of Neve Monosson.
-
C.
Otzias
Otzias is a coastal village and beach resort on the Greek island of Kea in the Cyclades.
-
D.
Hanoch
Hanoch is a biblical figure listed in the Hebrew Bible as one of the descendants of Abraham through Keturah and Midian.
-
E.
Savyon
Savyon is an affluent residential town in central Israel known for its spacious villas, high standard of living, and proximity to Tel Aviv.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5087b081909d6042bfe8d8a306 |
completed | March 9, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562c0ecb48190b3def058eaf49dd3 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.