Triple
T3211016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simeon |
E67279
|
entity |
| Predicate | nameInHebrew |
P6449
|
FINISHED |
| Object | שִׁמְעוֹן |
E67279
|
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: שִׁמְעוֹן | Statement: [Simeon, nameInHebrew, שִׁמְעוֹן]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: שִׁמְעוֹן Context triple: [Simeon, nameInHebrew, שִׁמְעוֹן]
-
A.
Simeon
chosen
Simeon is a biblical figure, one of the twelve sons of Jacob and a progenitor of one of the tribes of Israel.
-
B.
Shmuel
Shmuel is the Hebrew form of the biblical name Samuel, commonly used in Jewish religious and cultural contexts.
-
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.
Eleazar
Eleazar is a masculine given name of Hebrew origin, traditionally associated with religious and historical figures.
-
E.
Eleazar ben Simon
Eleazar ben Simon was a first-century Jewish Zealot leader who played a major role in the Great Jewish Revolt against the Roman Empire.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaab886c48190b72e36d0ac855ffe |
completed | March 8, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2f3b7e5c48190a8fc84ae78d4bd66 |
completed | March 12, 2026, 5:11 p.m. |
Created at: March 8, 2026, 3:07 p.m.