Triple
T4422222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Winter Paralympics |
E95125
|
entity |
| Predicate | hasMedalTable |
P11178
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [1994 Winter Paralympics, hasMedalTable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedalTable Context triple: [1994 Winter Paralympics, hasMedalTable, yes]
-
A.
hasMedalCount
Indicates the relationship between an entity and the number of medals it possesses or has been awarded.
-
B.
medalTableLeader
Indicates that an entity is currently leading the medal table, typically having the highest overall medal standing compared to others.
-
C.
wonMedalAt
Indicates that an entity received a medal as a result of participating in a specific event or competition.
-
D.
thirdInMedalTable
Indicates that an entity finished in third place in a ranking of medal counts (a medal table), typically in a competition or multi-sport event.
-
E.
hasStandings
chosen
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554a0e7c8190b704d00d07b1857d |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.