Triple
T31317154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USBMR1400128 |
E798626
|
entity |
| Predicate | associatedRecordingTitle |
P194200
|
FINISHED |
| Object | Shake It Off |
E227284
|
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: Shake It Off | Statement: [USBMR1400128, associatedRecordingTitle, Shake It Off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRecordingTitle Context triple: [USBMR1400128, associatedRecordingTitle, Shake It Off]
-
A.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
B.
associatedTitleType
Indicates the type or category of a title that is linked or related to another entity or primary title.
-
C.
originalCastRecordingReleaseDate
Indicates the date on which the original cast recording of a production was first released.
-
D.
recordingsKnownAs
chosen
Indicates that one recording is known, referred to, or identified by a particular alternative name or title.
-
E.
laterRecordedIn
Indicates that the referenced information or event was documented or captured at a later time in the specified source or record.
- F. None of above.
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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d660ffc8190a1b9e35c0c401a02 |
completed | June 11, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.