Triple
T36196121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adding Machine: A Musical |
E1047128
|
entity |
| Predicate | originalPlayTitle |
P108532
|
FINISHED |
| Object | The Adding Machine |
E150436
|
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: The Adding Machine | Statement: [Adding Machine: A Musical, originalPlayTitle, The Adding Machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlayTitle Context triple: [Adding Machine: A Musical, originalPlayTitle, The Adding Machine]
-
A.
playTitle
Indicates the title or name assigned to a play in a relationship between a play entity and its textual label.
-
B.
originalTitleName
chosen
Indicates that one entity is the original or primary title name associated with another entity.
-
C.
originalTitleOfWork
Indicates that one work is the original title under which another work was first created, published, or released.
-
D.
originalTitleUsedIn
Indicates that an entity’s original title is used in or associated with a particular work, edition, or context.
-
E.
playWithinPlayTitle
Indicates that one play is presented as a play within another play, and this predicate gives the title of that embedded play.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a394d2c266c81908c6e721e7902fe5a |
completed | June 22, 2026, 2:56 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.