Triple
T36406347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWF World Tour |
E896757
|
entity |
| Predicate | governsRankingPeriod |
P203887
|
FINISHED |
| Object | 52-week rolling ranking |
—
|
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: 52-week rolling ranking | Statement: [BWF World Tour, governsRankingPeriod, 52-week rolling ranking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsRankingPeriod Context triple: [BWF World Tour, governsRankingPeriod, 52-week rolling ranking]
-
A.
peakFIFARankingPeriod
Indicates the time period during which an entity (typically a national football team) held its highest-ever FIFA world ranking.
-
B.
regulatoryPeriod
Indicates the specific time span during which a regulation, rule, or regulatory framework is in effect or applicable.
-
C.
conferralPeriod
Indicates the time span during which a degree, title, or honor is formally awarded or conferred.
-
D.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
E.
jurisdictionPeriod
Indicates the time span during which a particular authority or entity holds legal or official jurisdiction over something.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0238010fa481909b07a5c22aa0abde |
completed | May 11, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_6a0236cfdcb481908323b67b925c76d9 |
completed | May 11, 2026, 8:06 p.m. |
| PDg | Predicate description generation | batch_6a02380061088190b77e9d6e44817444 |
completed | May 11, 2026, 8:11 p.m. |
Created at: May 3, 2026, 4:10 p.m.