Triple
T18319840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Sheema Classic |
E438842
|
entity |
| Predicate | upgradeToGroup1 |
P96864
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Dubai Sheema Classic, upgradeToGroup1, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradeToGroup1 Context triple: [Dubai Sheema Classic, upgradeToGroup1, 2002]
-
A.
upgradedToGroup1
chosen
Indicates that an entity has been elevated or transitioned to a higher-status category or group labeled "Group 1".
-
B.
upgradedToGroup1From
Indicates that an entity has been elevated or transitioned into group 1 status from another specified source group or category.
-
C.
promotedToGroup2
Indicates that an entity has been advanced or elevated in status, role, or membership into a second-level group or category.
-
D.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
E.
upgradeGoal
Indicates that an entity has a target or intended improvement to a higher level, version, or state relative to its current condition.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa4d3308190883714e1ef6a1d84 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.