Triple
T31269342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balak |
E797339
|
entity |
| Predicate | offeredPaymentTo |
P26126
|
FINISHED |
| Object | Balaam |
—
|
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: Balaam | Statement: [Balak, offeredPaymentTo, Balaam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredPaymentTo Context triple: [Balak, offeredPaymentTo, Balaam]
-
A.
offeredRewardTo
chosen
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
B.
offeredAmount
Indicates the specific quantity or value that one party proposes to give or pay to another in the context of an offer.
-
C.
rewardOfferedBy
Indicates that a reward is provided or promised by one entity to another, typically as an incentive or compensation for a specific action or outcome.
-
D.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
E.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 29, 2026, 9:13 p.m.