Triple
T19779105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampere Theatre |
E475084
|
entity |
| Predicate | isProfessionalTheatre |
P16508
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tampere Theatre, isProfessionalTheatre, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProfessionalTheatre Context triple: [Tampere Theatre, isProfessionalTheatre, true]
-
A.
isPartOfTheater
Indicates that one entity functions as a component, section, or subdivision within a larger theater (such as a theater building, complex, or organizational unit).
-
B.
partOfTheatre
Indicates that one entity is a component, section, or subdivision of a theatre.
-
C.
theatreType
chosen
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
D.
relatedTheatre
Indicates that there is an association or connection between an entity and a theatre, such as relevance, involvement, or contextual linkage.
-
E.
theaterProduction
Indicates a relationship where a theatrical work is produced or staged, typically linking the production event to the play, venue, or organizing 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538230488190b45cd8aaec658f7f |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.