Triple
T4758493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rugby sevens |
E105644
|
entity |
| Predicate | addedToOlympicProgrammeFor |
P15215
|
FINISHED |
| Object | 2016 Summer Olympics |
—
|
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: 2016 Summer Olympics | Statement: [rugby sevens, addedToOlympicProgrammeFor, 2016 Summer Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedToOlympicProgrammeFor Context triple: [rugby sevens, addedToOlympicProgrammeFor, 2016 Summer Olympics]
-
A.
OlympicStatus
chosen
Indicates that an entity holds a particular status or role in relation to the Olympic Games (e.g., being an Olympic sport, event, athlete, or host).
-
B.
openedForOlympics
Indicates that something was opened or inaugurated specifically in preparation for or in conjunction with the Olympic Games.
-
C.
olympicOpeningDate
Indicates the calendar date on which a specific edition of the Olympic Games officially begins with its opening ceremony.
-
D.
OlympicGamesParticipated
Indicates that an entity has taken part as a competitor in one or more editions of the Olympic Games.
-
E.
olympicDebut
Indicates the event or year in which an entity first participated 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650c11f4819098cd1f490f711dc8 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.