Triple
T24021046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DP World Tour Championship, Dubai |
E594821
|
entity |
| Predicate | isSeasonEndingEventOf |
P82427
|
FINISHED |
| Object | European Tour |
—
|
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: European Tour | Statement: [DP World Tour Championship, Dubai, isSeasonEndingEventOf, European Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeasonEndingEventOf Context triple: [DP World Tour Championship, Dubai, isSeasonEndingEventOf, European Tour]
-
A.
endSeason
Indicates the action or event of bringing a particular season, series, or period to a close.
-
B.
regularSeasonEndEvent
Indicates the event that marks the conclusion of a regular season in a competition or league.
-
C.
seasonCulminatesIn
Indicates that a particular season reaches its peak, conclusion, or defining outcome in the specified event or state.
-
D.
isCulminatingEventOf
chosen
Indicates that an event represents the final or peak outcome within a larger process, sequence, or series of related events.
-
E.
seasonFinaleOf
Indicates that one event, episode, or installment serves as the concluding or final part of a particular season of a series 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.