Triple
T31674258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BALCO doping scandal |
E808355
|
entity |
| Predicate | involvedSport |
P67409
|
FINISHED |
| Object | track and field |
—
|
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: track and field | Statement: [BALCO doping scandal, involvedSport, track and field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedSport Context triple: [BALCO doping scandal, involvedSport, track and field]
-
A.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
-
B.
relatedSport
chosen
Indicates that there is an association or connection between an entity and a particular sport.
-
C.
sportFounded
Indicates that an entity (such as a sports team, club, or organization) was established or created by another entity.
-
D.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
E.
inSportDiscipline
Indicates that an entity participates, competes, or is involved in a specific sport discipline or event.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 30, 2026, 11:02 p.m.