Triple
T38303008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine men’s national gymnastics team |
E1032271
|
entity |
| Predicate | OlympicTeamEvent |
P151547
|
FINISHED |
| Object | men’s team all‑around |
—
|
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: men’s team all‑around | Statement: [Ukraine men’s national gymnastics team, OlympicTeamEvent, men’s team all‑around]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OlympicTeamEvent Context triple: [Ukraine men’s national gymnastics team, OlympicTeamEvent, men’s team all‑around]
-
A.
olympicTeamRelated
Indicates that there is a relationship involving an Olympic team, such as membership, representation, or official association with that team.
-
B.
OlympicMedalEvent
Indicates that an entity represents a specific Olympic Games event in which medals are awarded.
-
C.
olympicEventType
chosen
Indicates the specific category or discipline of an event within the Olympic Games.
-
D.
olympicGoldMedalInEvent
Indicates that an entity has won an Olympic gold medal in a specified sporting event.
-
E.
olympicCompetition
Indicates that an entity participates in or is involved with a competition that is part of 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.