Triple
T32057194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada national wheelchair rugby team |
E818649
|
entity |
| Predicate | homeCountryNPC |
P174438
|
FINISHED |
| Object | Canadian Paralympic Committee |
—
|
NE NERFINISHED |
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: Canadian Paralympic Committee | Statement: [Canada national wheelchair rugby team, homeCountryNPC, Canadian Paralympic Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountryNPC Context triple: [Canada national wheelchair rugby team, homeCountryNPC, Canadian Paralympic Committee]
-
A.
homeCountryBoard
Indicates that an entity serves on the board of directors in the entity’s own home country.
-
B.
nativeCountry
Indicates the country in which an entity (typically a person) was born or is originally from.
-
C.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an entity.
-
D.
hostNationality
Indicates the national affiliation or citizenship of the host in a given hosting relationship or context.
-
E.
mainCountry
Indicates that one country is the primary or most significant country associated with a given entity or context.
- F. None of above. chosen
Provenance (4 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_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:21 a.m.