Triple
T24981763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nethanel son of Zuar |
E625186
|
entity |
| Predicate | offeredSacrificeFor |
P160832
|
FINISHED |
| Object | Tribe of Issachar |
—
|
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: Tribe of Issachar | Statement: [Nethanel son of Zuar, offeredSacrificeFor, Tribe of Issachar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredSacrificeFor Context triple: [Nethanel son of Zuar, offeredSacrificeFor, Tribe of Issachar]
-
A.
offeredSacrificeOn
chosen
Indicates that one entity performed a sacrificial offering upon or at another entity (such as an altar, location, or occasion).
-
B.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
C.
resultOfSacrifice
Indicates that something exists or occurs as the outcome or consequence of a sacrificial act.
-
D.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
E.
sacrificeAcceptedBy
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
- F. None of above.
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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:02 a.m.