Triple
T31802202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India national badminton team |
E811769
|
entity |
| Predicate | hasParaTeam |
P198191
|
FINISHED |
| Object | India para-badminton national team |
—
|
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: India para-badminton national team | Statement: [India national badminton team, hasParaTeam, India para-badminton national team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParaTeam Context triple: [India national badminton team, hasParaTeam, India para-badminton national team]
-
A.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
B.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
-
C.
hasCountryTeamIn
Indicates that a country has a corresponding team participating in or associated with a particular context, such as an event, league, or organization.
-
D.
hasMenTeam
Indicates that an entity possesses, is associated with, or fields a men’s team.
-
E.
hasSubteam
Indicates that one team is a subordinate or component team within another, larger team.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: April 30, 2026, 11:42 p.m.