Triple
T24021068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DP World Tour Championship, Dubai |
E594821
|
entity |
| Predicate | roundsFormat |
P68186
|
FINISHED |
| Object | 72-hole stroke play |
—
|
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: 72-hole stroke play | Statement: [DP World Tour Championship, Dubai, roundsFormat, 72-hole stroke play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundsFormat Context triple: [DP World Tour Championship, Dubai, roundsFormat, 72-hole stroke play]
-
A.
roundFormat
Indicates the specific structure, rules, or style in which a particular round of an event, game, or process is conducted.
-
B.
roundsStructure
chosen
Indicates that one entity defines or specifies the organization, sequence, or format of rounds within a process, event, or system.
-
C.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
D.
roundCount
Indicates the number of discrete rounds or iterations that have occurred or are allocated within a process, event, or interaction.
-
E.
firstRoundFormat
Indicates the specific structure or rules used to organize and play the initial round of a multi-round event or competition.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5aaf8588190b266557d573504b8 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:43 p.m.