Triple
T21750206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBSF World Cup |
E536892
|
entity |
| Predicate | athleteCategory |
P33092
|
FINISHED |
| Object | men |
—
|
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 | Statement: [IBSF World Cup, athleteCategory, men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: athleteCategory Context triple: [IBSF World Cup, athleteCategory, men]
-
A.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
B.
typeOfAthlete
chosen
Indicates that one entity is an athlete and the other specifies the kind or category of athlete they are.
-
C.
sportsCategory
Indicates that one entity is classified as a type or category within the domain of sports to which the other entity belongs.
-
D.
athletesFrom
Indicates that one or more athletes originate from, represent, or are associated with a particular place or organization.
-
E.
sportsIdentity
Indicates that an entity’s identity, role, or affiliation is defined in the context of sports (e.g., as an athlete, team, or sports-related organization).
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a79fb74819098a247c4f31598a8 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.