Triple
T6426441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleazar the priest |
E128069
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Eleazar |
E193643
|
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: Eleazar | Statement: [Eleazar the priest, givenName, Eleazar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eleazar Context triple: [Eleazar the priest, givenName, Eleazar]
-
A.
Eleazar
chosen
Eleazar is a masculine given name of Hebrew origin, traditionally associated with religious and historical figures.
-
B.
Eleazar Avaran
Eleazar Avaran was a Jewish warrior of the Maccabean revolt, renowned for his heroic death in battle against the Seleucid forces.
-
C.
Eleazar ben Ya'ir
Eleazar ben Ya'ir was a 1st-century Jewish Zealot leader best known for commanding the Sicarii rebels at Masada during the First Jewish–Roman War.
-
D.
Eleazar the priest
Eleazar the priest is a biblical high priest of Israel, son of Aaron, who helped lead and oversee the distribution of the Promised Land after Joshua’s conquests.
-
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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0691f944c81909d4e5d8ef9e494b6 |
completed | March 22, 2026, 10:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640e339108190bbb74c688de574cc |
completed | March 27, 2026, 8:33 a.m. |
Created at: March 22, 2026, 4:44 p.m.