Triple
T21380143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prostějov |
E527327
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Nádudvar |
—
|
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: Nádudvar | Statement: [Prostějov, hasTwinTown, Nádudvar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nádudvar Context triple: [Prostějov, hasTwinTown, Nádudvar]
-
A.
Nádudvar
chosen
Nádudvar is a town in eastern Hungary known for its agricultural traditions and location within the Northern Great Plain region.
-
B.
Dombóvár
Dombóvár is a town in southern Hungary known as an important local transport and economic center within Tolna County.
-
C.
Hajdúdorog
Hajdúdorog is a town in northeastern Hungary known as a center of the Hungarian Greek Catholic Church.
-
D.
Vasvár
Vasvár is a small historic town in western Hungary known for its medieval heritage and role as a former county seat.
-
E.
Tiszaújváros
Tiszaújváros is an industrial town in northeastern Hungary known for its large chemical and energy industries and its location along the Tisza 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0cdab8c8190a7eebe6e5961ee75 |
completed | April 22, 2026, 11:28 a.m. |
Created at: April 16, 2026, 5:11 p.m.