Triple
T31674282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BALCO doping scandal |
E808355
|
entity |
| Predicate | sportsAuthority |
P174860
|
FINISHED |
| Object | United States Olympic 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: United States Olympic Committee | Statement: [BALCO doping scandal, sportsAuthority, United States Olympic Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsAuthority Context triple: [BALCO doping scandal, sportsAuthority, United States Olympic Committee]
-
A.
sportsBrand
Indicates that one entity is a sports-related brand or label associated with the other entity.
-
B.
sportsGoodsShare
Indicates a relationship where one entity shares or distributes sports-related goods with or to another entity.
-
C.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
D.
tenantSport
Indicates that a tenant participates in or is associated with a particular sport.
-
E.
sportFounded
Indicates that an entity (such as a sports team, club, or organization) was established or created by another entity.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: April 30, 2026, 11:02 p.m.