Triple
T37161597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghostwriter (single) |
E920675
|
entity |
| Predicate | isWellKnownTrackOf |
P182622
|
FINISHED |
| Object | RJD2 |
—
|
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: RJD2 | Statement: [Ghostwriter (single), isWellKnownTrackOf, RJD2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWellKnownTrackOf Context triple: [Ghostwriter (single), isWellKnownTrackOf, RJD2]
-
A.
isLeadTrackOf
Indicates that a track serves as the primary or featured track associated with a particular release, album, or recording project.
-
B.
isHighProfileTrackOf
chosen
Indicates that a track is a particularly prominent, notable, or heavily featured item within a larger collection, such as an album, playlist, or catalog.
-
C.
isConceptTrackOf
Indicates that one entity is a conceptual or abstract version of another entity, typically representing the underlying idea or theme rather than a specific concrete instance.
-
D.
isClosingTrackOf
Indicates that a track serves as the final or last track on a specified release, album, or recording.
-
E.
ownerOfSomeTrack
Indicates that an entity has ownership of at least one track (such as a song, audio track, or similar item).
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.