Triple
T18421153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainy Day, Dream Away |
E442024
|
entity |
| Predicate | appearsOnSide |
P94492
|
FINISHED |
| Object | B (varies by pressing of Electric Ladyland) |
—
|
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 (varies by pressing of Electric Ladyland) | Statement: [Rainy Day, Dream Away, appearsOnSide, B (varies by pressing of Electric Ladyland)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOnSide Context triple: [Rainy Day, Dream Away, appearsOnSide, B (varies by pressing of Electric Ladyland)]
-
A.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
B.
operatesOnSide
Indicates that an action or process is performed specifically on a particular side or lateral aspect of an object or entity.
-
C.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
D.
wasOnSideOf
Indicates that one entity supported, aligned with, or took the same side as another entity in a conflict, dispute, or opposing situation.
-
E.
mayAppearOn
chosen
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a2be6bc8190b2812f77ff4cc960 |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.