Triple
T18245288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Maktoum Challenge Round 2 |
E436933
|
entity |
| Predicate | raceSurfaceAtMeydan2009_2014 |
P129040
|
FINISHED |
| Object | Tapeta |
—
|
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: Tapeta | Statement: [Al Maktoum Challenge Round 2, raceSurfaceAtMeydan2009_2014, Tapeta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceSurfaceAtMeydan2009_2014 Context triple: [Al Maktoum Challenge Round 2, raceSurfaceAtMeydan2009_2014, Tapeta]
-
A.
raceSurfaceHistory
chosen
Indicates the type of surface on which an entity has raced in the past, capturing its historical race-surface conditions.
-
B.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
C.
notableRaceTrackDepicted
Indicates that a work or representation depicts a race track that is considered notable or significant.
-
D.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
E.
racecourseHistory
Indicates that there is a historical record or past events associated with a particular racecourse.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e6fbac8190bf252c4337f50c29 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.