Triple
T4852497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ish-bosheth |
E108448
|
entity |
| Predicate | reignedOver |
P10353
|
FINISHED |
| Object | Ephraim |
E148887
|
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: Ephraim | Statement: [Ish-bosheth, reignedOver, Ephraim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ephraim Context triple: [Ish-bosheth, reignedOver, Ephraim]
-
A.
Ephraim
Ephraim is a small, historic village and popular tourist destination on the shores of Green Bay in Door County, Wisconsin.
-
B.
Ephraim
chosen
Ephraim is one of the tribes of Israel, traditionally descended from Joseph’s younger son and known for its prominence in the northern kingdom.
-
C.
Bene Ephraim
Bene Ephraim are a small Telugu-speaking community in India that identifies as Jewish, tracing their origins to ancient Israelite ancestry and practicing a form of Judaism blended with local traditions.
-
D.
Zabulon
Zabulon is a variant form of the biblical given name Zebulun, traditionally associated with one of the twelve tribes of Israel.
-
E.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d39a4cc81908e27f587729225b0 |
completed | March 20, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fac3fa0819085b7b732875a166b |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:26 p.m.