Triple
T796788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai World Cup |
E17039
|
entity |
| Predicate | firstRunningYear |
P19145
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Dubai World Cup, firstRunningYear, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunningYear Context triple: [Dubai World Cup, firstRunningYear, 1996]
-
A.
firstSeriesYear
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
-
B.
firstReportedYear
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
C.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
D.
firstOfficialClaimYear
Indicates the year in which an entity was first officially claimed, recorded, or recognized in an authoritative capacity.
-
E.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b172e88190a26d31c9075b81fb |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:38 p.m.