Triple
T24021063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DP World Tour Championship, Dubai |
E594821
|
entity |
| Predicate | associatedRanking |
P59486
|
FINISHED |
| Object | Official World Golf Ranking |
—
|
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: Official World Golf Ranking | Statement: [DP World Tour Championship, Dubai, associatedRanking, Official World Golf Ranking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRanking Context triple: [DP World Tour Championship, Dubai, associatedRanking, Official World Golf Ranking]
-
A.
relatedRanking
Indicates a relationship where one item’s ranking is connected to or influenced by another item’s ranking.
-
B.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
C.
partnerRank
Indicates the relative status or level assigned to a partner within a partnership or collaboration hierarchy.
-
D.
rankingScope
chosen
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
- 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.