Triple
T19617698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Viktoria Plzeň |
E470910
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Viktorka |
—
|
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: Viktorka | Statement: [FC Viktoria Plzeň, nickname, Viktorka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viktorka Context triple: [FC Viktoria Plzeň, nickname, Viktorka]
-
A.
Viktorka
chosen
Viktorka is the popular nickname of FC Viktoria Plzeň, a professional football club from Plzeň in the Czech Republic.
-
B.
Křemelná
Křemelná is a river in the Czech Republic that serves as one of the main headwaters of the Otava River.
-
C.
Viktoria
Viktoria is a feminine given name of Latin origin, commonly used in various European countries as a variant of "Victoria."
-
D.
Vinka
Vinka is a Finnish military training aircraft developed by Valmet for basic pilot instruction.
-
E.
Vasishka
Vasishka was a Kushan emperor who ruled parts of northern India and Central Asia in the early 3rd century CE, known primarily from his inscriptions and coinage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e346548190b12e38d716bdfc4f |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:43 p.m.