Triple
T27330307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostrava-Poruba municipal district |
E689779
|
entity |
| Predicate | hasPostwarArchitecture |
P185193
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ostrava-Poruba municipal district, hasPostwarArchitecture, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostwarArchitecture Context triple: [Ostrava-Poruba municipal district, hasPostwarArchitecture, yes]
-
A.
postwarResidence
Indicates the place where an entity lived or was based during the period following a specified war.
-
B.
exhibitedPostwar
Indicates that something was displayed or presented in an exhibition or similar context after a war or in the postwar period.
-
C.
postwarModification
Indicates that an entity has been altered, upgraded, or otherwise modified after the conclusion of a war or major conflict.
-
D.
notablePostwarUser
Indicates that an entity is recognized for its significant or prominent use of another entity in the period following a major war.
-
E.
regionAfter1945
Indicates that one region exists as the geopolitical or administrative successor of another region after the year 1945.
- F. None of above. chosen
Provenance (4 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 27, 2026, 11:37 a.m.