Triple
T12906328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walk This Way |
E308738
|
entity |
| Predicate | hasFamousCollaboration |
P8554
|
FINISHED |
| Object | Run-D.M.C. and Aerosmith version |
—
|
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: Run-D.M.C. and Aerosmith version | Statement: [Walk This Way, hasFamousCollaboration, Run-D.M.C. and Aerosmith version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousCollaboration Context triple: [Walk This Way, hasFamousCollaboration, Run-D.M.C. and Aerosmith version]
-
A.
hasNotableCollaborationType
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
-
B.
isOutsideMostFamousCollaborationsOf
Indicates that an entity is not among the most famous collaborations associated with another entity.
-
C.
notableCollaboration
chosen
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
D.
hasArtistSiblingCollaboration
Indicates that two artist siblings have worked together on a shared artistic project or collaboration.
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971831bd48190b0ecd13e7181bbc6 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.