Triple
T29427104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Místek |
E746324
|
entity |
| Predicate | isUrbanPartOf |
P80700
|
FINISHED |
| Object | Frýdek-Místek |
—
|
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: Frýdek-Místek | Statement: [Místek, isUrbanPartOf, Frýdek-Místek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanPartOf Context triple: [Místek, isUrbanPartOf, Frýdek-Místek]
-
A.
isUrbanSectionOf
chosen
Indicates that one area or segment is the part of a larger entity that lies within an urban or city environment.
-
B.
isUrbanCommuneOf
Indicates that one entity is an urban commune that administratively belongs to or is part of another entity (typically a higher-level territorial unit).
-
C.
isUrbanLocality
Indicates that a place is classified as an urban settlement or locality, as opposed to a rural area.
-
D.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
E.
isUrbanBackdropOf
Indicates that one entity serves as the city or metropolitan background setting against which another entity is situated, depicted, or occurs.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66ac6dc04819084203f8a4b51e676 |
completed | May 2, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:10 p.m.