Triple
T33805351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nothing On |
E866367
|
entity |
| Predicate | performedByFictionalTroupeIn |
P135020
|
FINISHED |
| Object | Noises Off |
—
|
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: Noises Off | Statement: [Nothing On, performedByFictionalTroupeIn, Noises Off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedByFictionalTroupeIn Context triple: [Nothing On, performedByFictionalTroupeIn, Noises Off]
-
A.
partOfFictionalGroup
Indicates that an entity belongs to or is a member of a specific fictional group, organization, or team.
-
B.
usedByFictionalGroup
Indicates that something is utilized or employed by a fictional group or organization within a narrative context.
-
C.
associatedWithComedyTeam
Indicates a relationship where an entity is or has been part of, working with, or otherwise linked to a specific comedy team.
-
D.
performingCompany
chosen
Indicates the company that carries out or executes a given performance, production, or event.
-
E.
fictionalTeam
Indicates that the related entities are members of, or otherwise associated with, the same fictional team within a narrative or imaginary context.
- 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 1:46 a.m.