Triple
T10958966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic badminton men's singles |
E258915
|
entity |
| Predicate | introducedAsOlympicSport |
P15214
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Olympic badminton men's singles, introducedAsOlympicSport, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsOlympicSport Context triple: [Olympic badminton men's singles, introducedAsOlympicSport, 1992]
-
A.
introducedSport
Indicates that an entity caused a particular sport to be brought into use, practice, or awareness within a specific context or place.
-
B.
firstAppearedInOlympics
chosen
Indicates the event or entity in which something made its debut appearance at the Olympic Games.
-
C.
olympicDebut
Indicates the event or year in which an entity first participated in the Olympic Games.
-
D.
openedForOlympics
Indicates that something was opened or inaugurated specifically in preparation for or in conjunction with the Olympic Games.
-
E.
OlympicStatus
Indicates that an entity holds a particular status or role in relation to the Olympic Games (e.g., being an Olympic sport, event, athlete, or host).
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77127b10481908ad1efafb2a338d1 |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.