Triple
T22310779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demoiselle Stakes |
E551504
|
entity |
| Predicate | hasGenderLimitation |
P15554
|
FINISHED |
| Object | female-only |
—
|
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: female-only | Statement: [Demoiselle Stakes, hasGenderLimitation, female-only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenderLimitation Context triple: [Demoiselle Stakes, hasGenderLimitation, female-only]
-
A.
hasGenderRequirement
chosen
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
B.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
C.
hasNumberOfGenders
Indicates the relationship that specifies how many distinct genders are associated with or recognized for a given entity.
-
D.
hasGenderNeutralEligibility
Indicates that an entity is eligible or applicable in a way that does not depend on or specify a particular gender.
-
E.
hasGenderConvention
Indicates that there is an established or customary way of assigning or expressing gender within a given context, system, or culture.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574e7fc0819080e3e85001ab2c90 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.