Triple
T26792932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stevie Wayne |
E670564
|
entity |
| Predicate | voiceHeardThrough |
P84907
|
FINISHED |
| Object | late-night radio show |
—
|
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: late-night radio show | Statement: [Stevie Wayne, voiceHeardThrough, late-night radio show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceHeardThrough Context triple: [Stevie Wayne, voiceHeardThrough, late-night radio show]
-
A.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
B.
voiceWork
Indicates that one entity performs or contributes voice acting or vocal performance work for another entity or creative production.
-
C.
voiceOutcome
Indicates the result or consequence produced by a particular voice action, command, or vocal interaction.
-
D.
heardBy
chosen
Indicates that a sound, message, or communication produced by one entity is perceived or received auditorily by another entity.
-
E.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f619bd27908190ac9152693dd37658 |
completed | May 2, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:17 a.m.