Triple
T35542723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Behave Yourself |
E1027105
|
entity |
| Predicate | hasBsideOrAsideRelationTo |
P15273
|
FINISHED |
| Object | Green Onions |
—
|
NE NERFINISHED |
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: Green Onions | Statement: [Behave Yourself, hasBsideOrAsideRelationTo, Green Onions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBsideOrAsideRelationTo Context triple: [Behave Yourself, hasBsideOrAsideRelationTo, Green Onions]
-
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.
hasBsideStatus
Indicates that one item (typically a song or track) holds the status of being the B-side counterpart to another primary item (such as an A-side single).
-
C.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
D.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
E.
hasASideOf
Indicates that one entity possesses or includes a particular side or face as part of its structure or boundary.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.