Triple
T19279767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plzeň–Domažlice railway line |
E482155
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Domažlice |
—
|
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: Domažlice | Statement: [Plzeň–Domažlice railway line, connects, Domažlice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Domažlice Context triple: [Plzeň–Domažlice railway line, connects, Domažlice]
-
A.
Domažlice
chosen
Domažlice is a historic town in the western Czech Republic known for its well-preserved medieval center and rich Chodové folk traditions.
-
B.
Jizbice
Jizbice is a small locality that forms part of the town of Náchod in the Hradec Králové Region of the Czech Republic.
-
C.
Říčany
Říčany is a town in the Czech Republic, located just southeast of Prague and known as a popular residential and commuter suburb with historical roots.
-
D.
Ruzyně
Ruzyně is a district in the western part of Prague, Czech Republic, best known as the location of the city’s main international airport.
-
E.
Slaný
Slaný is a historic town in the Czech Republic known for its medieval center and location northwest of Prague.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbf817c819098745ed365cda4a9 |
completed | April 20, 2026, 10:11 a.m. |
Created at: April 10, 2026, 1:30 p.m.