Triple
T35153018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XVI Olympic Winter Games Organizing Committee |
E1015043
|
entity |
| Predicate | editionNumberOfGamesOrganized |
P181186
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [XVI Olympic Winter Games Organizing Committee, editionNumberOfGamesOrganized, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editionNumberOfGamesOrganized Context triple: [XVI Olympic Winter Games Organizing Committee, editionNumberOfGamesOrganized, 16]
-
A.
numberOfTournaments
Indicates the total count of tournaments associated with or participated in by an entity.
-
B.
gamesHeldEvery
Indicates that games are conducted with a regular frequency or on every occurrence of a specified time interval or condition.
-
C.
totalGamesManaged
Indicates the total number of games that an entity has managed in its role (e.g., as a coach or manager).
-
D.
eventEditionNumber
chosen
Indicates the ordinal number assigned to a specific edition or occurrence of a recurring event.
-
E.
editionNumberOfTournament
Indicates the specific sequential edition number assigned to a given tournament within its overall series or history.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78cefb12c8190a955da746e14799f |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.