Triple
T31391281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrisongs |
E800737
|
entity |
| Predicate | hasNotableSongInCatalog |
P88822
|
FINISHED |
| Object | My Sweet Lord |
—
|
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: My Sweet Lord | Statement: [Harrisongs, hasNotableSongInCatalog, My Sweet Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSongInCatalog Context triple: [Harrisongs, hasNotableSongInCatalog, My Sweet Lord]
-
A.
hasNotableSongType
Indicates that an entity is associated with a specific type or category of notable song.
-
B.
hasNotableSongWithBand
Indicates that an artist or individual is associated with a band through a song that is considered notable or significant.
-
C.
notableSongsIncluded
chosen
Indicates that certain notable or significant songs are included as part of the referenced entity (such as an album, playlist, or collection).
-
D.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
E.
hasNotableSongNumber
Indicates that an entity is associated with a specific song identified by its notable number or index within a collection or sequence.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: April 29, 2026, 9:19 p.m.