Triple
T27610138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killer |
E700290
|
entity |
| Predicate | featuresUncreditedArtist |
P193928
|
FINISHED |
| Object | Seal |
E35256
|
NE 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: Seal | Statement: [Killer, featuresUncreditedArtist, Seal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresUncreditedArtist Context triple: [Killer, featuresUncreditedArtist, Seal]
-
A.
featuresSongwriterCovered
Indicates that one entity includes or highlights a songwriter whose work has been covered in a song or performance by another entity.
-
B.
hasUnknownSongwriter
Indicates that the songwriter associated with a work is not known or has not been identified.
-
C.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
-
D.
featuresVariousArtists
Indicates that something (typically a creative work) includes contributions from multiple distinct artists rather than a single primary artist.
-
E.
featuresReRecordedSong
Indicates that an entity (such as an album, release, or performance) includes a song that has been recorded again in a new version distinct from its original recording.
- F. None of above. chosen
Provenance (5 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12da8486888190b3c228233b90facb |
completed | May 24, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 27, 2026, 2:11 p.m.