Triple
T34373688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smoking/No Smoking |
E882228
|
entity |
| Predicate | isAdaptationOfPlaysCycle |
P141025
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Smoking/No Smoking, isAdaptationOfPlaysCycle, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdaptationOfPlaysCycle Context triple: [Smoking/No Smoking, isAdaptationOfPlaysCycle, yes]
-
A.
theatricalCycle
Indicates a recurring sequence of theatrical events, performances, or productions that are grouped together as a unified cycle.
-
B.
adaptedAsPlayBy
Indicates that a work has been transformed or reinterpreted into a play by a particular adapter.
-
C.
hasStagePlayCounterpart
Indicates that one work has a corresponding or equivalent version in the form of a stage play.
-
D.
usedInStageAdaptationsOf
Indicates that something (such as a work, element, or material) is employed or incorporated in stage adaptations of another work or source.
-
E.
stageAdaptation
chosen
Indicates that one work has been adapted into a performance intended for the stage, such as a play or musical.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.