Triple
T14889391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neusatz |
E359712
|
entity |
| Predicate | alternativeNameOf |
P39
|
FINISHED |
| Object | Újvidék |
E357860
|
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: Újvidék | Statement: [Neusatz, alternativeNameOf, Újvidék]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Újvidék Context triple: [Neusatz, alternativeNameOf, Újvidék]
-
A.
Újvidék
chosen
Újvidék is the Hungarian name for Novi Sad, a major cultural and economic center in northern Serbia and the capital of the autonomous province of Vojvodina.
-
B.
Újpest
Újpest is a northern district of Budapest, Hungary, known for its residential neighborhoods, industrial heritage, and the Újpest FC football club.
-
C.
Újbuda
Újbuda is a major residential and commercial district on the Buda side of Budapest, known for its universities, cultural venues, and riverside areas along the Danube.
-
D.
Győr
Győr is a historic city in northwestern Hungary, known as an important regional cultural and economic center at the confluence of the Danube, Rába, and Rábca rivers.
-
E.
Dunaújváros
Dunaújváros is an industrial city in central Hungary known for its steel production and post-war socialist urban planning.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f6cf5c8190b6b28f58fafe5d59 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbb7b1e48190b55c40e0cb837446 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 2:09 a.m.