Triple
T28551201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night Race Schladming |
E722888
|
entity |
| Predicate | typicalDisciplineGender |
P166271
|
FINISHED |
| Object | Men's slalom |
—
|
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: Men's slalom | Statement: [Night Race Schladming, typicalDisciplineGender, Men's slalom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDisciplineGender Context triple: [Night Race Schladming, typicalDisciplineGender, Men's slalom]
-
A.
hasTypicalGenderAssociation
Indicates that one entity is commonly or culturally associated with a particular gender more than with other genders.
-
B.
typeDiscipline
Indicates that an entity is associated with, categorized under, or characterized by a particular discipline or field of study.
-
C.
genderOfCompetitors
chosen
Indicates the gender category or composition of the participants involved in a competition or competitive event.
-
D.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
E.
admissionGender
Indicates the gender-based criteria or classification applied in the context of admission or entry decisions.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: April 28, 2026, 3:42 a.m.