Triple
T5349051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gumm Sisters act |
E124126
|
entity |
| Predicate | entertainmentField |
P30079
|
FINISHED |
| Object | live musical entertainment |
—
|
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: live musical entertainment | Statement: [The Gumm Sisters act, entertainmentField, live musical entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entertainmentField Context triple: [The Gumm Sisters act, entertainmentField, live musical entertainment]
-
A.
entertainmentType
chosen
Indicates the kind or category of entertainment associated with an entity or event.
-
B.
inFilmAndTV
Indicates that the subject appears or is featured within the context of film and television works.
-
C.
popularFilmIndustry
Indicates that an entity has a widely recognized and well-liked film industry that attracts significant audience interest and attention.
-
D.
inPopularCulture
Indicates that an entity is referenced, depicted, or otherwise present within works or discussions of popular culture.
-
E.
theater
Indicates that an entity is a theater or is functioning in the role of a theater (a venue where performances or films are shown).
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd860ea7088190ad7be14132927d17 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.