Triple
T1279979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We’ve Got Tonight |
E27300
|
entity |
| Predicate | hasBSide |
P15273
|
FINISHED |
| Object | varies by release |
—
|
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: varies by release | Statement: [We’ve Got Tonight, hasBSide, varies by release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBSide Context triple: [We’ve Got Tonight, hasBSide, varies by release]
-
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.
hasViewingSide
Indicates that one entity serves as the side or surface of another entity that is intended to be viewed or observed.
-
C.
onAlbumSide
Indicates that a particular track or song appears on a specified side (e.g., Side A or Side B) of an album.
-
D.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
E.
supportedSide
Indicates that one entity backed, favored, or provided assistance to a particular side or party in a conflict, dispute, or competition.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c092eb688190bf42bbd59e4ff289 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.