Triple
T32934301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Badminton Federation |
E842485
|
entity |
| Predicate | memberCountAtFounding |
P191712
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [International Badminton Federation, memberCountAtFounding, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberCountAtFounding Context triple: [International Badminton Federation, memberCountAtFounding, 9]
-
A.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
B.
foundedWithStudentsCount
Indicates that an entity was founded with the involvement of a specific number of students, capturing the student count at the time of its founding.
-
C.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
-
D.
numberOfCoFounders
Indicates the count of individuals who jointly founded a given entity.
-
E.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 1, 2026, 1:20 a.m.