Triple
T12523419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maldon Mud Race |
E299375
|
entity |
| Predicate | participantDressCode |
P2738
|
FINISHED |
| Object | fancy dress costumes |
—
|
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: fancy dress costumes | Statement: [Maldon Mud Race, participantDressCode, fancy dress costumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantDressCode Context triple: [Maldon Mud Race, participantDressCode, fancy dress costumes]
-
A.
hasDressCode
chosen
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
B.
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.
-
C.
usualAttire
Indicates the type of clothing an entity typically wears in ordinary or characteristic situations.
-
D.
costumeDesignEmphasisOn
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
E.
wearsOnUniform
Indicates that an item is part of and is worn as a component of a uniform.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.