Triple
T10450238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedlčany |
E246401
|
entity |
| Predicate | hasCadastralArea |
P90148
|
FINISHED |
| Object | Sedlčany |
E246401
|
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: Sedlčany | Statement: [Sedlčany, hasCadastralArea, Sedlčany]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sedlčany Context triple: [Sedlčany, hasCadastralArea, Sedlčany]
-
A.
Sedlčany
chosen
Sedlčany is a small historic town in the Czech Republic known for its traditional cheese production and location on the Mastník River.
-
B.
Svidník
Svidník is a small town in northeastern Slovakia known for its World War II memorials, open-air museum of folk architecture, and its location in the culturally rich Šariš region.
-
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.
Slaný
Slaný is a historic town in the Czech Republic known for its medieval center and location northwest of Prague.
-
E.
Ružomberok
Ružomberok is a town in northern Slovakia known for its location in the Liptov region and its historical and cultural significance.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe09af04819083db42f4de4cb0a9 |
completed | April 7, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95e5749208190b37848f0945bd92d |
completed | April 10, 2026, 8:32 p.m. |
Created at: April 6, 2026, 12:17 p.m.