Triple
T31227378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic 9-50797 |
E796178
|
entity |
| Predicate | albumAssociation |
P102247
|
FINISHED |
| Object | Off the Wall |
—
|
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: Off the Wall | Statement: [Epic 9-50797, albumAssociation, Off the Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: albumAssociation Context triple: [Epic 9-50797, albumAssociation, Off the Wall]
-
A.
albumDisc
Indicates that one entity is a specific disc (or disc number) within a multi-disc album represented by the other entity.
-
B.
albumAppearance
Indicates that an entity appears on, is featured in, or is included as part of a particular album.
-
C.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
D.
otherAlbum
Indicates that one album is different from and distinct to another album, typically used to contrast or distinguish between two albums.
-
E.
hasAssociatedAlbum
chosen
Indicates that an entity is linked to a specific album with which it is related or connected.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:10 p.m.