Triple
T26109136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Lewis (The Sunshine Boys) |
E658635
|
entity |
| Predicate | hasPerformanceBackground |
P69787
|
FINISHED |
| Object | vaudeville |
—
|
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: vaudeville | Statement: [Al Lewis (The Sunshine Boys), hasPerformanceBackground, vaudeville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceBackground Context triple: [Al Lewis (The Sunshine Boys), hasPerformanceBackground, vaudeville]
-
A.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
B.
hasPerformerBackground
chosen
Indicates that an entity has a specific background, experience, or history as a performer.
-
C.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
D.
hasBackgroundSample
Indicates that an entity is associated with or linked to a corresponding background sample used for comparison or reference.
-
E.
hasPerformanceLocation
Indicates that an event, performance, or show takes place at a specified location or venue.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 8 p.m.