Triple
T18671423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Union at the Olympics |
E456484
|
entity |
| Predicate | summerGamesParticipated |
P7486
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Soviet Union at the Olympics, summerGamesParticipated, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerGamesParticipated Context triple: [Soviet Union at the Olympics, summerGamesParticipated, 9]
-
A.
OlympicGamesParticipated
chosen
Indicates that an entity has taken part as a competitor in one or more editions of the Olympic Games.
-
B.
associatedOlympicGames
Indicates a relationship where something is linked to, or occurs in connection with, a specific edition of the Olympic Games.
-
C.
olympicGames
Indicates that an entity is an edition or instance of the Olympic Games event.
-
D.
previousSummerOlympics
Indicates that one Olympic Games event occurred immediately before another in the chronological sequence of Summer Olympic Games.
-
E.
olympicParticipationType
Indicates the specific role or category of involvement an entity has in the Olympic Games (e.g., as an athlete, team, official, or other participation type).
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b21d2481908e1b8b583bfabb72 |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.