Triple
T1138775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zlín |
E23399
|
entity |
| Predicate | regionSeatOf |
P3877
|
FINISHED |
| Object | Zlín Region authorities |
—
|
LITERAL 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: Zlín Region authorities | Statement: [Zlín, regionSeatOf, Zlín Region authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSeatOf Context triple: [Zlín, regionSeatOf, Zlín Region authorities]
-
A.
hasSeatOfAdministration
Indicates that an administrative body or jurisdiction has a specific place or location that serves as its central seat of governance or administration.
-
B.
cityAsSeatOfGovernment
Indicates that a city serves as the official seat or location of a government’s central authority or administration.
-
C.
capitalCityOfRegion
chosen
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
-
D.
municipalitySeat
Indicates that one entity serves as the administrative center or capital (seat) of a municipality.
-
E.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
- F. None of above.
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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.