Triple
T1470912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Me Baby |
E27131
|
entity |
| Predicate | hasRecordingEra |
P22765
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Rock Me Baby, hasRecordingEra, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingEra Context triple: [Rock Me Baby, hasRecordingEra, 1960s]
-
A.
recordingEra
chosen
Indicates the historical time period or era during which the recording was made.
-
B.
historicallyRecordedSince
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
-
C.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
D.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
E.
hasRecordingContract
Indicates that an entity is formally bound by an agreement to produce recordings for another entity, typically a record label or similar organization.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d9dd4c8190ba840a9255cd1293 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.