Triple
T19917747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Handicap |
E478707
|
entity |
| Predicate | raceSexRestriction |
P15554
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Metropolitan Handicap, raceSexRestriction, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceSexRestriction Context triple: [Metropolitan Handicap, raceSexRestriction, none]
-
A.
raceTypeBySex
Indicates that a race or competition is categorized or defined based on the sex of its participants.
-
B.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
C.
hasGenderRequirement
chosen
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
D.
sportRestriction
Indicates a limitation, prohibition, or specific condition placed on participating in a sport or sports-related activity.
-
E.
isSingleSex
Indicates that the entity involves or is restricted to only one biological sex or gender, rather than being mixed or coeducational.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65995bd60819097cfad003dd29731 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.