Triple
T30367200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Boomers |
E772450
|
entity |
| Predicate | associatedSportFamily |
P67409
|
FINISHED |
| Object | team sports |
—
|
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: team sports | Statement: [Australian Boomers, associatedSportFamily, team sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSportFamily Context triple: [Australian Boomers, associatedSportFamily, team sports]
-
A.
sportsAssociationViaFamily
Indicates a relationship where an entity is associated with a sport or sports organization through a family member’s involvement rather than their own direct participation.
-
B.
relatedSport
chosen
Indicates that there is an association or connection between an entity and a particular sport.
-
C.
parentSport
Indicates that one sport is the broader or more general category from which another sport is derived or classified.
-
D.
sportingCodeFamily
Indicates that one sporting code belongs to, or is categorized under, a broader family of related sporting codes.
-
E.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:58 p.m.