Triple
T15725021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaron and his sons |
E381197
|
entity |
| Predicate | collectiveIncludes |
P119934
|
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: [Aaron and his sons, collectiveIncludes, Ithamar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ithamar Context triple: [Aaron and his sons, collectiveIncludes, Ithamar]
-
A.
Ithamar
chosen
Ithamar is a biblical figure, a son of Aaron who served as a priest in ancient Israel.
-
B.
Huelel
Huelel is the self-designated name (endonym) used by the Esselen people, an Indigenous group native to the central coast of California.
-
C.
Yaphit
Yaphit is a gelatinous, shape-shifting engineer serving aboard the exploratory spaceship in the science-fiction TV series "The Orville."
-
D.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
-
E.
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.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142df48e8819083a48d3b7b3f7f5d |
completed | April 16, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82f8b88081909855d3da0346fa25 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:46 a.m.