Triple
T26682863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabez Stone |
E672660
|
entity |
| Predicate | motiveForDeal |
P19457
|
FINISHED |
| Object | seek prosperity |
—
|
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: seek prosperity | Statement: [Jabez Stone, motiveForDeal, seek prosperity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motiveForDeal Context triple: [Jabez Stone, motiveForDeal, seek prosperity]
-
A.
motive
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
B.
motivationFor
chosen
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
C.
reasonForAcquisition
Indicates the underlying purpose, motive, or justification for which one entity acquires another entity or asset.
-
D.
reasonForSale
Indicates the underlying cause, motivation, or circumstance that explains why something is being sold.
-
E.
openingMotive
Indicates the initial reason, trigger, or intent that prompts an action or event to begin.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:21 a.m.