Triple
T15963820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Won’t Dance |
E387132
|
entity |
| Predicate | notableRecordingType |
P120633
|
FINISHED |
| Object | duet |
—
|
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: duet | Statement: [I Won’t Dance, notableRecordingType, duet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRecordingType Context triple: [I Won’t Dance, notableRecordingType, duet]
-
A.
notableRecordingMedium
Indicates that an entity is notably recorded, documented, or expressed using a particular medium or format.
-
B.
notableRecordingTradition
Indicates that there exists a significant or historically important tradition of recording or documenting something associated with the subject.
-
C.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
D.
notableRecordingSession
Indicates that a particular recording session is especially significant or noteworthy in relation to the subject.
-
E.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:53 a.m.