Triple
T18183073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsom Derby Festival |
E435338
|
entity |
| Predicate | genderQualificationOaks |
P15554
|
FINISHED |
| Object | three-year-old fillies |
—
|
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: three-year-old fillies | Statement: [Epsom Derby Festival, genderQualificationOaks, three-year-old fillies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderQualificationOaks Context triple: [Epsom Derby Festival, genderQualificationOaks, three-year-old fillies]
-
A.
admissionGender
Indicates the gender-based criteria or classification applied in the context of admission or entry decisions.
-
B.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
C.
hasGenderRequirement
chosen
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
D.
overseesGenderCategory
Indicates that one entity has responsibility for supervising, managing, or administering a particular gender category associated with another entity.
-
E.
eligiblePlayersGender
Indicates that the relationship specifies which player genders are allowed or considered eligible in a given context.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffc432c8190af53da5256dc476c |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.