Triple
T27773268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li Yundi |
E699113
|
entity |
| Predicate | competitionEdition |
P159408
|
FINISHED |
| Object | 14th International Chopin Piano Competition |
—
|
NE NERFINISHED |
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: 14th International Chopin Piano Competition | Statement: [Li Yundi, competitionEdition, 14th International Chopin Piano Competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionEdition Context triple: [Li Yundi, competitionEdition, 14th International Chopin Piano Competition]
-
A.
competitionEditionOf
chosen
Indicates that one entity is a specific edition or instance of a broader recurring competition or contest.
-
B.
competitionDepicted
Indicates that a competitive event or rivalry between entities is shown or represented in some medium or context.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
editionOfCompetition
Indicates that one entity is a specific edition or iteration of a recurring competition or tournament.
-
E.
competitionSeries
Indicates that one entity is a recurring competitive event or series in which the other entity participates or is featured.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 5:03 p.m.