Triple
T13550416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC Kladno |
E323629
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | SK Kladno |
E323629
|
NE 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: SK Kladno | Statement: [HC Kladno, formerName, SK Kladno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SK Kladno Context triple: [HC Kladno, formerName, SK Kladno]
-
A.
HC Kladno
chosen
HC Kladno is a Czech professional ice hockey club based in Kladno, historically one of the country’s prominent teams and known for producing several notable Czech players.
-
B.
MFK Karviná
MFK Karviná is a professional football club from Karviná in the Czech Republic that competes in the country’s league system and is known for its regional rivalry with FC Baník Ostrava.
-
C.
SK Benešov
SK Benešov is a Czech football club based in the town of Benešov.
-
D.
SK Slavia Prague
SK Slavia Prague is one of the most successful and historic football clubs in the Czech Republic, based in Prague and competing in the country’s top division.
-
E.
SK Líšeň
SK Líšeň is a Czech football club from the Líšeň district of Brno, known for competing in the national league system and its local rivalry with FC Zbrojovka Brno.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaff0a6548190b8cde5084cef0061 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75da4e19c819090d649b60a2dd410 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:46 p.m.