Triple
T18110985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascot Gold Cup |
E433471
|
entity |
| Predicate | dressCodeAssociation |
P2738
|
FINISHED |
| Object | Royal Ascot formal dress traditions |
—
|
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: Royal Ascot formal dress traditions | Statement: [Ascot Gold Cup, dressCodeAssociation, Royal Ascot formal dress traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dressCodeAssociation Context triple: [Ascot Gold Cup, dressCodeAssociation, Royal Ascot formal dress traditions]
-
A.
hasDressCode
chosen
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
B.
typicallyWornWith
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
-
C.
usesDressing
Indicates that one entity applies or employs a particular dressing (such as a sauce, covering, or treatment) in relation to another entity or context.
-
D.
usualAttire
Indicates the type of clothing an entity typically wears in ordinary or characteristic situations.
-
E.
typicalWear
Indicates that one entity is commonly or characteristically worn by the other in typical situations or contexts.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.