Triple
T18374413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ithamar |
E446273
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Abihu |
—
|
NE NERFINISHED |
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: Abihu | Statement: [Ithamar, sibling, Abihu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abihu Context triple: [Ithamar, sibling, Abihu]
-
A.
Abihu
chosen
Abihu is a biblical figure, one of the sons of Aaron who served as a priest and was killed for offering unauthorized fire before God.
-
B.
Nadab
Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
-
C.
Nadab
Nadab was a king of the northern Kingdom of Israel in the Hebrew Bible, known as the son and short-reigning royal heir of Jeroboam I.
-
D.
Phinehas
Phinehas is a biblical priest and grandson of Aaron, noted for his zealous defense of Israel’s covenant with God in the Hebrew Bible.
-
E.
Hezron
Hezron is a biblical figure listed among the descendants of Judah and an ancestor in the genealogies leading to King David and, in Christian tradition, to Jesus.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51757a75c8190814db973ae1a86cd |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 10:45 a.m.