Triple
T4793884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeroboam I |
E106665
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Nadab |
E468575
|
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: Nadab | Statement: [Jeroboam I, child, Nadab]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nadab Context triple: [Jeroboam I, child, Nadab]
-
A.
Nadab
Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
-
B.
Nadab
chosen
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.
-
C.
Abihu
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.
-
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.
Korah
Korah is a biblical figure known for leading a rebellion against Moses and Aaron during the Israelites’ wilderness journey.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd66088d588190839acfbac6e1c3dd |
completed | March 20, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4d96f7e88190be4ba5c7ceb07608 |
completed | March 21, 2026, 7:49 a.m. |
Created at: March 20, 2026, 1:22 p.m.