Triple
T28659894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athletics at the Summer Olympics |
E725436
|
entity |
| Predicate | isCoreSportOf |
P15165
|
FINISHED |
| Object | Olympic Games |
—
|
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: Olympic Games | Statement: [Athletics at the Summer Olympics, isCoreSportOf, Olympic Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoreSportOf Context triple: [Athletics at the Summer Olympics, isCoreSportOf, Olympic Games]
-
A.
includesSport
chosen
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
B.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
C.
primarySport
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
-
D.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
-
E.
isNonOlympicSport
Indicates that a sport is not included as an official event in the Olympic Games.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:57 a.m.