Triple
T23868438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canary Dutch |
E592653
|
entity |
| Predicate | openingProductionOf |
P70612
|
FINISHED |
| Object | Morosco 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: Morosco Theatre | Statement: [Canary Dutch, openingProductionOf, Morosco Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingProductionOf Context triple: [Canary Dutch, openingProductionOf, Morosco Theatre]
-
A.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
C.
openingPerformance
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
-
D.
openingStage
Indicates the initial phase or first part of a process, event, or sequence in which subsequent stages will follow.
-
E.
openedWithProduction
chosen
Indicates that something (such as an event, show, or process) began or was initiated using a particular production or production setup.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae643448190863c44df5f026482 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.