Triple
T6885055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Issachar |
E158896
|
entity |
| Predicate | supported |
P1853
|
FINISHED |
| Object | Deborah |
E109288
|
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: Deborah | Statement: [Tribe of Issachar, supported, Deborah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deborah Context triple: [Tribe of Issachar, supported, Deborah]
-
A.
Deborah
chosen
Deborah is a prominent biblical prophetess and judge of Israel known for her leadership and role in delivering the Israelites from Canaanite oppression.
-
B.
Dinah
Dinah is a biblical figure mentioned in the Book of Genesis as the daughter of Jacob and Leah.
-
C.
Avigail
Avigail is a feminine given name, commonly used in Hebrew, that corresponds to the name Abigail.
-
D.
Jael
Jael is a biblical heroine celebrated in the Book of Judges for killing the Canaanite commander Sisera and thus securing victory for Israel.
-
E.
Yaël
Yaël is a French feminine given name of Hebrew origin, commonly borne by contemporary public figures such as politicians and artists.
- 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d90a2590819092ff253dd66ebe8b |
completed | March 27, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c742dc8d608190b2a8e9c1f46e1420 |
completed | March 28, 2026, 2:54 a.m. |
Created at: March 27, 2026, 2:23 p.m.