Triple
T18313465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Guineas Stakes |
E438690
|
entity |
| Predicate | typicalSexRestriction |
P32136
|
FINISHED |
| Object | colts |
—
|
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 | Statement: [2000 Guineas Stakes, typicalSexRestriction, colts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSexRestriction Context triple: [2000 Guineas Stakes, typicalSexRestriction, colts]
-
A.
standardSex
Indicates that two entities share the same biological sex or gender classification.
-
B.
requiresCelibacyFor
Indicates that one entity imposes a requirement of celibacy on another entity as a condition for participation, membership, role, or status.
-
C.
isSingleSex
chosen
Indicates that the entity involves or is restricted to only one biological sex or gender, rather than being mixed or coeducational.
-
D.
demographicRestriction
Indicates that participation, access, or applicability is limited or conditioned based on specific demographic characteristics (such as age, gender, ethnicity, or similar attributes).
-
E.
hasSexualityCharacteristic
Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021b7e2c81908cd3b6684ab899f6 |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.