Triple
T13595627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'm More Than Happy (I'm Satisfied) |
E324810
|
entity |
| Predicate | hasBsideRole |
P15273
|
FINISHED |
| Object | B-side track |
—
|
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: B-side track | Statement: [I'm More Than Happy (I'm Satisfied), hasBsideRole, B-side track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBsideRole Context triple: [I'm More Than Happy (I'm Satisfied), hasBsideRole, B-side track]
-
A.
hasBside
chosen
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
-
B.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
C.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
D.
hasTeamSide
Indicates that an entity is associated with or belongs to a particular side or faction of a team within a competitive or collaborative context.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0590558819080ccc5874a650b1e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.