Triple
T5373269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Othniel |
E108900
|
entity |
| Predicate | rewardReceived |
P25342
|
FINISHED |
| Object | marriage to Achsah |
—
|
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: marriage to Achsah | Statement: [Othniel, rewardReceived, marriage to Achsah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardReceived Context triple: [Othniel, rewardReceived, marriage to Achsah]
-
A.
rewardFulfilledFor
chosen
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
-
B.
rewardSignal
Indicates that one entity provides a signal representing feedback or incentive (such as a reward or penalty) to guide another entity’s behavior or learning process.
-
C.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
D.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
E.
rewardRedemption
Indicates the act of exchanging accumulated rewards, points, or benefits for goods, services, or other forms of value.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.