Triple
T22875887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Ease Me In |
E567321
|
entity |
| Predicate | hasNotableAudience |
P140994
|
FINISHED |
| Object | Grateful Dead fans |
—
|
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: Grateful Dead fans | Statement: [Don't Ease Me In, hasNotableAudience, Grateful Dead fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAudience Context triple: [Don't Ease Me In, hasNotableAudience, Grateful Dead fans]
-
A.
notableAudience
chosen
Indicates that an entity is especially well-known, relevant, or targeted among a particular audience or group of people.
-
B.
hasAudienceReach
Indicates the extent or scope of people or groups that are exposed to, can access, or are targeted by a particular entity, message, or activity.
-
C.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
D.
hasNotableNumber
Indicates that an entity is associated with a specific number that is considered significant, distinctive, or noteworthy in some context.
-
E.
hasNotableSpeaker
Indicates that an event, gathering, or occasion features a speaker who is distinguished or noteworthy in some significant way.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f58a7308190b710bdf013e2e114 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:39 p.m.