Triple
T28147579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy’s Rare Records |
E714524
|
entity |
| Predicate | stageAdaptationStar |
P141305
|
FINISHED |
| Object | Lenny Henry |
—
|
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: Lenny Henry | Statement: [Rudy’s Rare Records, stageAdaptationStar, Lenny Henry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageAdaptationStar Context triple: [Rudy’s Rare Records, stageAdaptationStar, Lenny Henry]
-
A.
stageAdaptation
Indicates that one work has been adapted into a performance intended for the stage, such as a play or musical.
-
B.
stageAdaptationForm
Indicates that one work is a stage adaptation (e.g., play, musical, performance script) derived from another work.
-
C.
adaptationStar
Indicates that one work is an adaptation of another, with the subject being the adapted work and the object being the original source.
-
D.
adaptationStarred
chosen
Indicates that a person has a starring role in an adaptation of an original work.
-
E.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 9:57 p.m.