Triple
T27701879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Santaland Diaries |
E698447
|
entity |
| Predicate | stageAdaptationForm |
P165093
|
FINISHED |
| Object | one-man show |
—
|
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: one-man show | Statement: [The Santaland Diaries, stageAdaptationForm, one-man show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageAdaptationForm Context triple: [The Santaland Diaries, stageAdaptationForm, one-man show]
-
A.
stageAdaptation
Indicates that one work has been adapted into a performance intended for the stage, such as a play or musical.
-
B.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
C.
stageModel
Indicates a relationship where one entity serves as or defines the staging or intermediate version of a model for another entity.
-
D.
stageElement
Indicates that one entity functions as a component or part within the structure or configuration of another entity.
-
E.
adaptationStage
Indicates the phase or level of progress an entity has reached in adjusting or responding to a particular environment, condition, or change.
- F. None of above. chosen
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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 2:57 p.m.