Triple
T3872927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Derby |
E92428
|
entity |
| Predicate | sexRestriction |
P28993
|
FINISHED |
| Object | colts and 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: colts and fillies | Statement: [Kentucky Derby, sexRestriction, colts and fillies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexRestriction Context triple: [Kentucky Derby, sexRestriction, colts and fillies]
-
A.
isSingleSex
Indicates that the entity involves or is restricted to only one biological sex or gender, rather than being mixed or coeducational.
-
B.
sexType
Indicates the specific category or type of sexual activity or sexual relationship involved between entities.
-
C.
hasGenderRequirement
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
D.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
E.
demographicRestriction
chosen
Indicates that participation, access, or applicability is limited or conditioned based on specific demographic characteristics (such as age, gender, ethnicity, or similar attributes).
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.