Triple
T4555840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EJ’s Neat-O Stat of the Night |
E120474
|
entity |
| Predicate | typicalPresenterRole |
P51719
|
FINISHED |
| Object | studio host |
—
|
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: studio host | Statement: [EJ’s Neat-O Stat of the Night, typicalPresenterRole, studio host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPresenterRole Context triple: [EJ’s Neat-O Stat of the Night, typicalPresenterRole, studio host]
-
A.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typicalAnnouncerRole
chosen
Indicates that an entity commonly or characteristically serves in a particular announcer role in relevant contexts.
-
C.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
-
D.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
E.
promotionalRole
Indicates that an entity serves in a capacity focused on promoting, advertising, or publicizing another entity, product, or activity.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5813af948190b10b02dadf6496bf |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.