Triple
T32057199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada national wheelchair rugby team |
E818649
|
entity |
| Predicate | teamGenderPolicy |
P111986
|
FINISHED |
| Object | mixed-sex |
—
|
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: mixed-sex | Statement: [Canada national wheelchair rugby team, teamGenderPolicy, mixed-sex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamGenderPolicy Context triple: [Canada national wheelchair rugby team, teamGenderPolicy, mixed-sex]
-
A.
hasGenderPolicy
Indicates that an entity has adopted, implemented, or is governed by a specific policy related to gender issues or gender equality.
-
B.
genderOfMascot
Indicates the gender associated with a particular mascot.
-
C.
hasGenderedTeams
Indicates that the entity organizes or participates in teams that are separated or defined based on gender.
-
D.
hasGenderedTeam
Indicates that a team is organized or classified according to the gender of its members.
-
E.
eligiblePlayersGender
chosen
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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f0a9dc81908245f7583767a26f |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:21 a.m.