Triple
T31185027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "I'm Down" |
E795014
|
entity |
| Predicate | sidePositionOnSingle |
P171229
|
FINISHED |
| Object | B-side to "Help!" |
—
|
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 to "Help!" | Statement: ["I'm Down", sidePositionOnSingle, B-side to "Help!"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sidePositionOnSingle Context triple: ["I'm Down", sidePositionOnSingle, B-side to "Help!"]
-
A.
singleSideOf
Indicates that one entity constitutes a single side or face of another entity, typically within a larger multi-sided structure or object.
-
B.
singleSide
Indicates that the relationship or action involves only one side or participant, without a corresponding or reciprocal counterpart.
-
C.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
D.
singleAorBside
Indicates that exactly one of the two related entities is on side A or side B, but not both simultaneously.
-
E.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
- F. None of above. chosen
Provenance (4 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6f01e881908fa84f5d429d37ae |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:08 p.m.