Triple
T33805599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Frayn bibliography |
E866377
|
entity |
| Predicate | includesNotablePlay |
P9490
|
FINISHED |
| Object | Noises Off |
E246810
|
NE 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: Noises Off | Statement: [Michael Frayn bibliography, includesNotablePlay, Noises Off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNotablePlay Context triple: [Michael Frayn bibliography, includesNotablePlay, Noises Off]
-
A.
notablePlay
chosen
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
B.
notablePlayType
Indicates that a particular type or category of play is especially significant or characteristic for the subject.
-
C.
notablePlayQuarter
Indicates that a particular play or action in a game is considered especially significant or noteworthy within a specific quarter.
-
D.
notablePlayPlayer
Indicates that a player is notably associated with a particular play, such as by making a significant or memorable contribution in it.
-
E.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
- F. None of above.
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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0357f9670081908a7ba1cd46a0b46a |
completed | May 12, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36d5c75ebc81909855e0b33e1939c6 |
completed | June 20, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_6a03575e3258819093303248d1569f95 |
completed | May 12, 2026, 4:37 p.m. |
Created at: May 1, 2026, 1:46 a.m.