Triple
T33213472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diaper Dandy |
E850220
|
entity |
| Predicate | partOfIdiolectOf |
P64609
|
FINISHED |
| Object | Dick Vitale |
—
|
NE NERFINISHED |
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: Dick Vitale | Statement: [Diaper Dandy, partOfIdiolectOf, Dick Vitale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfIdiolectOf Context triple: [Diaper Dandy, partOfIdiolectOf, Dick Vitale]
-
A.
partOfLinguisticVariety
chosen
Indicates that one linguistic variety (such as a dialect, register, or style) is a constituent or subset of another, broader linguistic variety.
-
B.
partOfLanguage
Indicates that one linguistic element belongs to, is included within, or is a component of a particular language.
-
C.
spokenInPartOf
Indicates that a language or dialect is spoken within a specific subregion or part of a larger geographic or administrative area.
-
D.
vernacularOf
Indicates that one language or dialect is the everyday, locally used form corresponding to another, more general or standard language.
-
E.
hasDialectalOriginOf
Indicates that something originates from or is derived from a particular dialect.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 1, 2026, 1:30 a.m.