Triple
T31160823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Word of Mouth (1981 album) |
E794330
|
entity |
| Predicate | coverSource |
P72675
|
FINISHED |
| Object | Blackbird by The Beatles |
—
|
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: Blackbird by The Beatles | Statement: [Word of Mouth (1981 album), coverSource, Blackbird by The Beatles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverSource Context triple: [Word of Mouth (1981 album), coverSource, Blackbird by The Beatles]
-
A.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
B.
coverVersionBy
chosen
Indicates that one creative work is a cover version performed or produced by a particular artist or entity.
-
C.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
D.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
E.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 9:07 p.m.