Triple
T15849805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izhar |
E384303
|
entity |
| Predicate | brother |
P363
|
FINISHED |
| Object | Amram |
E446274
|
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: Amram | Statement: [Izhar, brother, Amram]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amram Context triple: [Izhar, brother, Amram]
-
A.
Amram
chosen
Amram is a biblical figure from the Hebrew Bible, known primarily as the father of Moses, Aaron, and Miriam and a descendant of Levi.
-
B.
Elkanah
Elkanah is a biblical figure known as the husband of Hannah and the father of the prophet Samuel in the Hebrew Bible.
-
C.
Shem
Shem is a biblical figure regarded as one of Noah’s sons and traditionally considered an ancestor of the Semitic peoples.
-
D.
Nachshon ben Amminadab
Nachshon ben Amminadab is a biblical figure from the Book of Exodus, traditionally revered as the first Israelite to step into the Red Sea in an act of pioneering faith and courage.
-
E.
Abram
Abram is a masculine given name of Hebrew origin, historically associated with the biblical patriarch later named Abraham.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14cab0fe48190bd6629e071761e91 |
completed | April 16, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa145f2dc819092db805806b6e1d5 |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 10, 2026, 4:50 a.m.