Triple
T6079063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zlín Region |
E135475
|
entity |
| Predicate | hasTraditionalRegion |
P14194
|
FINISHED |
| Object | Haná (partly) |
E382461
|
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: Haná (partly) | Statement: [Zlín Region, hasTraditionalRegion, Haná (partly)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haná (partly) Context triple: [Zlín Region, hasTraditionalRegion, Haná (partly)]
-
A.
Haná
chosen
Haná is a historical ethnographic region in central Moravia in the Czech Republic, known for its fertile agricultural land, distinctive folk traditions, and Hanakian dialect.
-
B.
Hannut
Hannut is a municipality in the French-speaking Walloon Region of Belgium, known for its rural character and location between Liège and Brussels.
-
C.
Hana
Hana is a small, remote town on the eastern coast of Maui, Hawaii, known for its lush landscapes, waterfalls, and the scenic Road to Hana.
-
D.
Hana
Hana is a person known primarily as the romantic partner of Kip.
-
E.
Hana
Hana is a common female given name of Hebrew origin, often associated with meanings like "grace" or "favor."
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0577209b88190afe5b1365cf6436d |
completed | March 22, 2026, 8:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d4dc7ec8190baeede11ac27e229 |
completed | March 23, 2026, 11 a.m. |
Created at: March 22, 2026, 4:11 p.m.