Triple
T27701878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Santaland Diaries |
E698447
|
entity |
| Predicate | stageAdaptationBy |
P141025
|
FINISHED |
| Object | Joe Mantello |
—
|
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: Joe Mantello | Statement: [The Santaland Diaries, stageAdaptationBy, Joe Mantello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageAdaptationBy Context triple: [The Santaland Diaries, stageAdaptationBy, Joe Mantello]
-
A.
stageAdaptation
chosen
Indicates that one work has been adapted into a performance intended for the stage, such as a play or musical.
-
B.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
C.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
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.
scriptAdaptationFrom
Indicates that a script is adapted or derived from a pre-existing source work (such as a book, play, or earlier script).
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:57 p.m.