Triple
T5301456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympia archaeological site |
E119989
|
entity |
| Predicate | earliestGamesHeld |
P58332
|
FINISHED |
| Object | 776 BCE |
—
|
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: 776 BCE | Statement: [Olympia archaeological site, earliestGamesHeld, 776 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestGamesHeld Context triple: [Olympia archaeological site, earliestGamesHeld, 776 BCE]
-
A.
firstGamesTraditionallyDated
Indicates that the subject’s earliest known or customary date of occurrence is based on traditional or conventional dating rather than precise historical evidence.
-
B.
isFirstWorldCupHeldIn
Indicates that a country's first participation in the FIFA World Cup took place in the specified host nation or location.
-
C.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
D.
firstKnownTournamentYear
chosen
Indicates the year in which a tournament was first known to have been held.
-
E.
isOneOfOldestConferencesIn
Indicates that a conference ranks among the oldest conferences within a specified location or domain.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.