Triple
T18319837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Sheema Classic |
E438842
|
entity |
| Predicate | firstRunAsGroup1 |
P131359
|
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, firstRunAsGroup1, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunAsGroup1 Context triple: [Dubai Sheema Classic, firstRunAsGroup1, 2002]
-
A.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
B.
firstRunTimePeriod
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
-
C.
firstClassRuns
Indicates that the subject has participated in official first-class cricket matches, with the object specifying the number or record of such runs scored.
-
D.
firstPerformedAs
Indicates the initial occasion or context in which an entity (such as a work, role, or piece) was performed by a particular performer or group.
-
E.
firstRunProducer
Indicates that the producer is responsible for the initial or original run of a production, such as the first airing, release, or performance.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.