Triple
T31269340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balak |
E797339
|
entity |
| Predicate | intendedAction |
P88492
|
FINISHED |
| Object | have Balaam curse the Israelites |
—
|
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: have Balaam curse the Israelites | Statement: [Balak, intendedAction, have Balaam curse the Israelites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedAction Context triple: [Balak, intendedAction, have Balaam curse the Israelites]
-
A.
plannedAction
Indicates that an action is intended or scheduled to occur in the future, but has not yet been executed.
-
B.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
C.
attemptedAction
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
D.
intendsTo
chosen
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
E.
promptedAction
Indicates that one entity initiates or triggers another entity to perform a specific action.
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 29, 2026, 9:13 p.m.