Triple
T33701497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Birling |
E863465
|
entity |
| Predicate | obtainsMoneyBy |
P131350
|
FINISHED |
| Object | stealing from his father’s business |
—
|
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: stealing from his father’s business | Statement: [Eric Birling, obtainsMoneyBy, stealing from his father’s business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obtainsMoneyBy Context triple: [Eric Birling, obtainsMoneyBy, stealing from his father’s business]
-
A.
MoneyInTheBankCashInBy
Indicates that a Money in the Bank contract is cashed in by a particular person or entity.
-
B.
earnedCurrency
chosen
Indicates that an entity has obtained a specified amount or type of currency as a result of some activity, work, or transaction.
-
C.
MoneyInTheBankCashInType
Indicates the manner or category of how a Money in the Bank contract is cashed in (e.g., timing, conditions, or style of the cash-in event).
-
D.
obtains
Indicates that one entity comes into possession or control of another entity, typically through some action or process.
-
E.
owedMoneyTo
Indicates that one entity has a financial obligation or debt that must be paid to another entity.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa8d59b88190832e66716f7170ab |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.