Triple
T34860169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Simson |
E1004844
|
entity |
| Predicate | lostMoneyTo |
P167519
|
FINISHED |
| Object | John Oakhurst |
—
|
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: John Oakhurst | Statement: [Tom Simson, lostMoneyTo, John Oakhurst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostMoneyTo Context triple: [Tom Simson, lostMoneyTo, John Oakhurst]
-
A.
lostFortuneDueTo
chosen
Indicates that one entity suffered a loss of wealth or assets as a result of the actions, influence, or circumstances associated with another entity.
-
B.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
C.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
D.
causedLossOf
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
-
E.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or context.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.