Triple
T29279998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human (The Killers single cover) |
E742345
|
entity |
| Predicate | coverForReleaseType |
P177145
|
FINISHED |
| Object | single |
—
|
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: single | Statement: [Human (The Killers single cover), coverForReleaseType, single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverForReleaseType Context triple: [Human (The Killers single cover), coverForReleaseType, single]
-
A.
coverVersionBy
Indicates that one creative work is a cover version performed or produced by a particular artist or entity.
-
B.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
C.
coverPosition
Indicates that one entity occupies or shields a specific position or area, providing coverage for it.
-
D.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
E.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
- F. None of above. chosen
Provenance (4 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 12:54 p.m.