Triple
T11879282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elis |
E282611
|
entity |
| Predicate | sportsEventOrigin |
P102024
|
FINISHED |
| Object | ancient Olympic Games |
—
|
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: ancient Olympic Games | Statement: [Elis, sportsEventOrigin, ancient Olympic Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsEventOrigin Context triple: [Elis, sportsEventOrigin, ancient Olympic Games]
-
A.
sportsEventHosted
Indicates that a particular sports event was organized, arranged, or held by a specified host entity (such as a venue, organization, or city).
-
B.
sportsAttraction
Indicates a relationship where an entity serves as a venue, site, or draw specifically for sports-related activities or events.
-
C.
sportEventTypeOrganized
Indicates that an entity organizes or is responsible for arranging a specific type of sports event.
-
D.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
E.
originalSport
Indicates that one sport is the initial or primary sport associated with an entity, often before any change, adaptation, or transition to another sport.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.