Triple
T33577622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branigan 2 |
E860068
|
entity |
| Predicate | featuresMusicalEra |
P38929
|
FINISHED |
| Object | 1980s pop sound |
—
|
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: 1980s pop sound | Statement: [Branigan 2, featuresMusicalEra, 1980s pop sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMusicalEra Context triple: [Branigan 2, featuresMusicalEra, 1980s pop sound]
-
A.
musicalEra
chosen
Indicates the historical musical period or style with which an entity (such as a composition, performance, or musician) is associated.
-
B.
playsMusicFromEra
Indicates that an entity performs or plays music that originates from, or is characteristic of, a specified historical era.
-
C.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
curatesEra
Indicates a relationship where an entity organizes, selects, or manages items, information, or works specifically associated with a particular historical or thematic era.
-
E.
recordingEra
Indicates the historical time period or era during which the recording was made.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
Created at: May 1, 2026, 1:40 a.m.