Triple
T31181098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenge Belt |
E794895
|
entity |
| Predicate | lastAwardedFor |
P107
|
FINISHED |
| Object | 1870 Open Championship |
—
|
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: 1870 Open Championship | Statement: [Challenge Belt, lastAwardedFor, 1870 Open Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastAwardedFor Context triple: [Challenge Belt, lastAwardedFor, 1870 Open Championship]
-
A.
lastAwarded
Indicates the most recent time or instance at which an entity received a particular award.
-
B.
holderAwardedFor
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
-
C.
awardFor
chosen
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
D.
formerlyAwardedIn
Indicates that an award or recognition was previously given in a particular context, time, or location but is no longer awarded there.
-
E.
awardedSince
Indicates that an entity has been receiving a particular award continuously from a specified starting time onward.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.