Triple
T25781779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invictus Games |
E649309
|
entity |
| Predicate | inauguralEventEndDate |
P159816
|
FINISHED |
| Object | 2014-09-14 |
—
|
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: 2014-09-14 | Statement: [Invictus Games, inauguralEventEndDate, 2014-09-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguralEventEndDate Context triple: [Invictus Games, inauguralEventEndDate, 2014-09-14]
-
A.
inauguralEventDate
Indicates the calendar date on which an entity’s first or inaugural event took place.
-
B.
inaugurationDate
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
-
C.
inaugurationDay
Indicates the specific day on which a formal ceremony is held to induct someone into an official position or office.
-
D.
inaugurationEvent
Indicates an event in which a person is formally installed or inducted into an official position or office.
-
E.
originalInaugurationDate
Indicates the date on which an entity (such as an office, institution, or facility) was first formally inaugurated or put into official operation.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe6175048190afd845628c74830e |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 5:38 a.m.