Triple
T19206347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Thornton |
E480242
|
entity |
| Predicate | usesWinningsFor |
P134965
|
FINISHED |
| Object | funding a search for a lost mine |
—
|
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: funding a search for a lost mine | Statement: [John Thornton, usesWinningsFor, funding a search for a lost mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWinningsFor Context triple: [John Thornton, usesWinningsFor, funding a search for a lost mine]
-
A.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
B.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
C.
winnerMake
Indicates that one entity causes or brings about another entity becoming the winner in a contest, competition, or selection process.
-
D.
hasPrizeMoney
Indicates that an entity awards, offers, or is associated with a specified amount of prize money.
-
E.
MagicWins
Indicates that one entity achieves victory over another through the use of magic or supernatural powers.
- F. None of above. chosen
Provenance (4 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f99d8ad0819098ebd4ee007149f1 |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:19 p.m.