Triple
T30762405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do Wah Diddy Diddy |
E783268
|
entity |
| Predicate | coverLabel |
P180642
|
FINISHED |
| Object | His Master’s Voice |
—
|
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: His Master’s Voice | Statement: [Do Wah Diddy Diddy, coverLabel, His Master’s Voice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverLabel Context triple: [Do Wah Diddy Diddy, coverLabel, His Master’s Voice]
-
A.
coversLabel
chosen
Indicates that one entity’s scope, content, or applicability includes or encompasses the label associated with another entity.
-
B.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
C.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
D.
coverSymbol
Indicates that one symbol or notation is used as a cover or representative marker for another entity in a given context.
-
E.
coverStatus
Indicates the current state or condition of coverage that applies to an entity, such as whether coverage is active, pending, expired, or otherwise classified.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:39 p.m.