Triple
T33470375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Těšín Theatre |
E857170
|
entity |
| Predicate | hasCzechStage |
P176660
|
FINISHED |
| Object | Česká scéna |
—
|
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: Česká scéna | Statement: [Těšín Theatre, hasCzechStage, Česká scéna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCzechStage Context triple: [Těšín Theatre, hasCzechStage, Česká scéna]
-
A.
czechName
Indicates that an entity has a name in the Czech language, specifying the Czech-language form of its name.
-
B.
hasStageIn
Indicates a relationship where one entity occurs, exists, or takes place within a particular stage or phase of another process, lifecycle, or sequence.
-
C.
lengthInCzechRepublic
Indicates the extent or measurement of something specifically within the geographic boundaries of the Czech Republic.
-
D.
hasAbbreviationInCzech
Indicates that an entity has a specific abbreviation or shortened form when expressed in the Czech language.
-
E.
hasStageStructure
Indicates that one entity possesses or is characterized by a particular stage-based structural organization defined by another entity.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:37 a.m.