Triple
T19784804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baal-hazor |
E475232
|
entity |
| Predicate | associatedWithPerson |
P37
|
FINISHED |
| Object | Amnon |
—
|
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: Amnon | Statement: [Baal-hazor, associatedWithPerson, Amnon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amnon Context triple: [Baal-hazor, associatedWithPerson, Amnon]
-
A.
Amnon
chosen
Amnon is a biblical figure known as the eldest son of King David, whose rape of his half-sister Tamar and subsequent murder by her brother Absalom sparked major turmoil in David’s household.
-
B.
Jonadab
Jonadab is a shrewd but morally dubious cousin of Amnon in the biblical narrative, known for advising Amnon in his plot against Tamar and later revealing knowledge of Absalom’s revenge.
-
C.
Shaul
Shaul is the Hebrew form of the name Saul, most famously associated with the first king of ancient Israel in the Hebrew Bible.
-
D.
Aviel
Aviel is a given name of Hebrew origin, often associated with Jewish and Israeli communities.
-
E.
Abinoam
Abinoam is a biblical figure mentioned in the Old Testament as the father of the Israelite military leader Barak.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.