Triple
T19673997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abinoam |
E472405
|
entity |
| Predicate | hasChild |
P369
|
FINISHED |
| Object | Barak |
E107162
|
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: Barak | Statement: [Abinoam, hasChild, Barak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barak Context triple: [Abinoam, hasChild, Barak]
-
A.
Barak
chosen
Barak is a biblical military leader in the Book of Judges who, alongside the prophetess Deborah, led Israel to victory over the Canaanite commander Sisera.
-
B.
Barak
Barak is a tough, streetwise assistant and later close ally to Tudor lawyer-detective Matthew Shardlake in C. J. Sansom’s historical mystery series.
-
C.
Asa Heshel
Asa Heshel is a member of the fictional Moskat family featured in Isaac Bashevis Singer’s novel "The Family Moskat."
-
D.
Avigdor
Avigdor is a Hebrew given name of biblical origin, traditionally used in Jewish communities.
-
E.
Natan
Natan is a masculine given name of Hebrew origin, commonly used in Jewish and Israeli communities and meaning "he gave."
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416e19d881909248c4f778f7147a |
completed | April 20, 2026, 3:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0787c08af48190a7253a74bca96aa6 |
completed | May 15, 2026, 8:53 p.m. |
Created at: April 10, 2026, 1:45 p.m.