Triple
T5671512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1959 Mediterranean Games |
E124988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mediterranean Games |
C16982
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Mediterranean Games Context triple: [1959 Mediterranean Games, instanceOf, Mediterranean Games]
-
A.
Mediterranean Games edition
chosen
A Mediterranean Games edition is a specific occurrence of the multi-sport event held among countries bordering the Mediterranean Sea, defined by its host city, year, participating nations, sports program, and organizational details.
-
B.
Panhellenic Games
Panhellenic Games were a series of ancient Greek athletic and religious festivals, including the Olympic, Pythian, Nemean, and Isthmian Games, held in honor of various gods and uniting city-states through competition and shared culture.
-
C.
Asian Games
The Asian Games is a multi-sport international event held every four years in which athletes from across Asia compete in a wide range of Olympic and regional sports under the governance of the Olympic Council of Asia.
-
D.
Commonwealth Games
The Commonwealth Games is an international multi-sport event held every four years, featuring athletes from nations and territories of the Commonwealth of Nations competing in a wide range of sports and disciplines.
-
E.
Spartan festival
A Spartan festival is a religious and civic celebration in ancient Sparta that combined ritual worship, athletic and musical competitions, communal feasting, and displays of military discipline to reinforce social cohesion and Spartan values.
- F. None of above.
Provenance (1 batch)
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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:43 p.m.