Triple
T32109420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceres Games |
E820075
|
entity |
| Predicate | typeOfSportingEvent |
P6316
|
FINISHED |
| Object | multi-sport event |
—
|
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: multi-sport event | Statement: [Ceres Games, typeOfSportingEvent, multi-sport event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSportingEvent Context triple: [Ceres Games, typeOfSportingEvent, multi-sport event]
-
A.
sportEventType
chosen
Indicates the specific kind or category of sport associated with a given sporting event.
-
B.
sportingEventAssociatedWith
Indicates that there is a relevant connection or involvement between a sporting event and another entity (such as a person, team, organization, or place).
-
C.
gameEventType
Indicates the specific kind or category of event that occurs within a game (e.g., start, pause, score, or end).
-
D.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
E.
sportEventTypeOrganized
Indicates that an entity organizes or is responsible for arranging a specific type of sports 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: May 1, 2026, 12:27 a.m.