Triple
T13778964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPC Swimming World Championships |
E331085
|
entity |
| Predicate | featuresGenderCategories |
P2577
|
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: [IPC Swimming World Championships, featuresGenderCategories, men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGenderCategories Context triple: [IPC Swimming World Championships, featuresGenderCategories, men]
-
A.
featuredGender
Indicates that a particular gender is highlighted, emphasized, or given primary focus in a given context or presentation.
-
B.
genderCategories
chosen
Indicates the classification of an entity into one or more gender-related categories or identities.
-
C.
isGenderSpecificCategory
Indicates that the category applies specifically to one gender rather than being gender-neutral.
-
D.
plugGender
Indicates that one entity’s connector has a specified gender (e.g., male, female, neutral) in relation to another connector or interface.
-
E.
usedByGender
Indicates that something is utilized, applied, or engaged in by entities of a specified gender.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0239cbfc81909064ac2457fdfff5 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:11 p.m.