Triple
T37001263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dofasco Centre for the Arts |
E915355
|
entity |
| Predicate | hasStudioTheatre |
P202271
|
FINISHED |
| Object | Studio Theatre |
—
|
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: Studio Theatre | Statement: [Dofasco Centre for the Arts, hasStudioTheatre, Studio Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudioTheatre Context triple: [Dofasco Centre for the Arts, hasStudioTheatre, Studio Theatre]
-
A.
hasStudio
Indicates that an entity (such as a film, game, or production) is associated with or produced by a particular studio.
-
B.
hasStudioProduction
Indicates that one entity is the studio responsible for producing the other entity (such as a film, series, or similar work).
-
C.
hasTheatricalStaging
Indicates that something (such as a work or event) is presented or realized through a theatrical staging or performance.
-
D.
hasStudiosIn
Indicates that an entity operates or maintains studio facilities located in a specified place or region.
-
E.
hasTheaterCollective
Indicates that one entity is associated with or belongs to a particular theater collective.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_6a00694e9e008190b7c941d2f7527dff |
completed | May 10, 2026, 11:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.