Triple
T3098943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reuben |
E64667
|
entity |
| Predicate | reasonForLossOfBirthright |
P41735
|
FINISHED |
| Object | offense involving his father’s concubine Bilhah |
—
|
LITERAL 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: offense involving his father’s concubine Bilhah | Statement: [Reuben, reasonForLossOfBirthright, offense involving his father’s concubine Bilhah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForLossOfBirthright Context triple: [Reuben, reasonForLossOfBirthright, offense involving his father’s concubine Bilhah]
-
A.
reasonForLossOfSuccessionRights
chosen
Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
-
B.
reasonForTribute
Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
-
C.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
D.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
E.
reasonForNoGrave
Indicates the circumstance or explanation for why an individual does not have a grave or burial site.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada269a9188190aada5b3799d4dfd7 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.