Triple
T27038040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovak Cup |
E681109
|
entity |
| Predicate | successorCompetitionInCzechRepublic |
P13377
|
FINISHED |
| Object | Czech Cup |
—
|
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: Czech Cup | Statement: [Czechoslovak Cup, successorCompetitionInCzechRepublic, Czech Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorCompetitionInCzechRepublic Context triple: [Czechoslovak Cup, successorCompetitionInCzechRepublic, Czech Cup]
-
A.
successorCompetition
chosen
Indicates that one competition directly follows another in sequence, serving as its successor in a series or timeline.
-
B.
numberOfGamesInCzechoslovakia
Indicates the total count of games that took place in Czechoslovakia.
-
C.
gamesWonByCzechoslovakia
Indicates that the referenced games or matches were won by Czechoslovakia.
-
D.
chartPositionCzechRepublic
Indicates the position or ranking of something on a chart specifically within the Czech Republic.
-
E.
successorInEurope
Indicates that one entity directly follows another in a succession or sequence specifically within the context of Europe.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 7:17 a.m.