Triple
T14865025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest I. kerülete |
E349593
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Dísz tér |
E1085840
|
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: Dísz tér | Statement: [Budapest I. kerülete, hasLandmark, Dísz tér]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dísz tér Context triple: [Budapest I. kerülete, hasLandmark, Dísz tér]
-
A.
Dísz tér
chosen
Dísz tér is a historic public square located in the Buda Castle District of Budapest, Hungary.
-
B.
Tisztviselőtelep
Tisztviselőtelep is a historic residential neighborhood in Budapest known for its early 20th-century urban design and middle-class civic servant housing.
-
C.
Parádfürdő
Parádfürdő is a spa village in northern Hungary known for its mineral springs and scenic location within the Mátra mountain region.
-
D.
Etelköz
Etelköz was the historical region in Eastern Europe where the migrating Magyars settled before conquering the Carpathian Basin.
-
E.
Dirdal
Dirdal is a small village in southwestern Norway, situated in a scenic valley within Gjesdal municipality in Rogaland county.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5761c688190b4477cb081554b51 |
completed | April 15, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe650e8aec8190acd4a9cb9cad2039 |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:55 a.m.