Triple
T16522577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | omnium |
E401354
|
entity |
| Predicate | olympicGenderCategory |
P7453
|
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: [omnium, olympicGenderCategory, men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: olympicGenderCategory Context triple: [omnium, olympicGenderCategory, men]
-
A.
sportGender
chosen
Indicates that a sport or sporting event is associated with a particular gender category (e.g., men's, women's, mixed).
-
B.
awardCategoryGender
Indicates that an award category is designated for recipients of a specific gender.
-
C.
hasFemaleCompetitors
Indicates that an entity participates in a competitive context where at least some of the competitors are female.
-
D.
winnerGender
Indicates the gender of the entity that is the winner in a given event or competition.
-
E.
eligiblePlayersGender
Indicates that the relationship specifies which player genders are allowed or considered eligible in a given context.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e8158cc8190aa77c6d37bd7ec76 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.