Triple
T24021389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Race to Dubai |
E594830
|
entity |
| Predicate | hasFinalEvent |
P128609
|
FINISHED |
| Object | DP World Tour Championship, Dubai |
—
|
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: DP World Tour Championship, Dubai | Statement: [Race to Dubai, hasFinalEvent, DP World Tour Championship, Dubai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalEvent Context triple: [Race to Dubai, hasFinalEvent, DP World Tour Championship, Dubai]
-
A.
hasFinalState
Indicates that an entity ultimately results in, transitions to, or ends in a specified final state or condition.
-
B.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
-
C.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
D.
hasFinalDrop
Indicates that an entity experiences or possesses a last or concluding decrease, reduction, or decline in some quantity, state, or value.
-
E.
hasFinale
chosen
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
- 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:47 p.m.