Triple
T28921171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blankety Blank (as Lily Savage) |
E733514
|
entity |
| Predicate | hasHostPersona |
P61233
|
FINISHED |
| Object | sharp‑tongued drag queen |
—
|
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: sharp‑tongued drag queen | Statement: [Blankety Blank (as Lily Savage), hasHostPersona, sharp‑tongued drag queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostPersona Context triple: [Blankety Blank (as Lily Savage), hasHostPersona, sharp‑tongued drag queen]
-
A.
hasPersona
chosen
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
B.
hasHostPersonality
Indicates that one entity serves as the host by exhibiting the primary personality or behavioral traits associated with another entity.
-
C.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
D.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
E.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 8:19 a.m.