Triple
T10452787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Back for Murder (stage) |
E246471
|
entity |
| Predicate | hasTheatricalForm |
P94120
|
FINISHED |
| Object | play in two acts |
—
|
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: play in two acts | Statement: [Go Back for Murder (stage), hasTheatricalForm, play in two acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheatricalForm Context triple: [Go Back for Murder (stage), hasTheatricalForm, play in two acts]
-
A.
theatricalReleaseWith
Indicates that two or more entities share the same theatrical release context, such as being released together or as part of the same theatrical event or distribution.
-
B.
servedInTheatres
Indicates that a film or performance was publicly exhibited in movie theaters or similar cinema venues.
-
C.
theatricalReleaseIn
Indicates that a film or performance was released or shown theatrically in a specified location or market.
-
D.
cinematicForm
Indicates that something is expressed, structured, or realized through the techniques, conventions, or medium of cinema or film.
-
E.
theaterType
Indicates the specific kind or category of theater associated with an entity (e.g., cinema, opera house, drama theater).
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0d73d48190acb687b96918e0cf |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:17 p.m.