Triple
T6413912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adonijah |
E127774
|
entity |
| Predicate | opposedBy |
P437
|
FINISHED |
| Object | Benaiah |
E476635
|
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: Benaiah | Statement: [Adonijah, opposedBy, Benaiah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Benaiah Context triple: [Adonijah, opposedBy, Benaiah]
-
A.
Benaiah
chosen
Benaiah was a prominent Israelite warrior and commander under King David and King Solomon, renowned for his bravery and loyalty in biblical accounts.
-
B.
Abishai
Abishai is a prominent Old Testament military leader and nephew of King David, known for his close association with his brother Joab and his role in David’s campaigns.
-
C.
Joab
Joab is a prominent military commander in the Hebrew Bible, known especially as King David’s ruthless yet loyal army leader.
-
D.
Shaul
Shaul is the Hebrew form of the name Saul, most famously associated with the first king of ancient Israel in the Hebrew Bible.
-
E.
Aviel
Aviel is a given name of Hebrew origin, often associated with Jewish and Israeli communities.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e5187c8190a6be1b934e0f1b3a |
completed | March 22, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c64bb5196c8190ab970afbe4f2a672 |
completed | March 27, 2026, 9:19 a.m. |
Created at: March 22, 2026, 4:42 p.m.