Triple
T6426446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleazar the priest |
E128069
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Ithamar |
E446273
|
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: Ithamar | Statement: [Eleazar the priest, sibling, Ithamar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ithamar Context triple: [Eleazar the priest, sibling, Ithamar]
-
A.
Ithamar
chosen
Ithamar is a biblical figure, a son of Aaron who served as a priest in ancient Israel.
-
B.
Reuel
Reuel is the middle name of famed English author and philologist J. R. R. Tolkien, used as part of his full name John Ronald Reuel Tolkien.
-
C.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
-
D.
Machlon
Machlon is a biblical figure mentioned in the Book of Ruth as one of Elimelech and Naomi’s sons, whose death leads to Ruth’s eventual marriage to Boaz.
-
E.
Huram
Huram is an alternative biblical form of the name Hiram, commonly associated with figures linked to the construction of Solomon’s Temple.
- 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.