Triple
T19841704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipany |
E476746
|
entity |
| Predicate | roadConnection |
P385
|
FINISHED |
| Object | Sabinov |
—
|
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: Sabinov | Statement: [Lipany, roadConnection, Sabinov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sabinov Context triple: [Lipany, roadConnection, Sabinov]
-
A.
Sabinov
chosen
Sabinov is a historic town in eastern Slovakia known for its well-preserved medieval center and role as a regional hub in the Šariš area.
-
B.
Sviblovo
Sviblovo is a Moscow Metro station on the Kaluzhsko–Rizhskaya Line serving the Sviblovo District in the city’s northeast.
-
C.
Sokolov
Sokolov is a town in the Karlovy Vary Region of the Czech Republic, known for its historical center and location in the Ohře River valley.
-
D.
Moravice
Moravice is a river in the northern part of the historical Moravia region of the Czech Republic.
-
E.
Bobrůvka
Bobrůvka is a river in the Czech Republic that flows through the Vysočina and South Moravian regions before joining the Svratka River.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65806375c8190a4f45f14aeb06515 |
completed | April 20, 2026, 4:44 p.m. |
Created at: April 10, 2026, 1:51 p.m.