Triple
T35359941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strawberry Letter 23 |
E1021447
|
entity |
| Predicate | hasNotableGuitaristOnCover |
P15267
|
FINISHED |
| Object | George Johnson |
E1021445
|
NE 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: George Johnson | Statement: [Strawberry Letter 23, hasNotableGuitaristOnCover, George Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGuitaristOnCover Context triple: [Strawberry Letter 23, hasNotableGuitaristOnCover, George Johnson]
-
A.
hasNotableCoverArtist
Indicates that an entity has a cover (e.g., of a book, album, or publication) created by a cover artist who is considered notable.
-
B.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
C.
hasGuitarist
Indicates that an entity has, employs, or is associated with a guitarist as part of it.
-
D.
hasCoverArtFeaturing
chosen
Indicates that one entity’s cover art visually features or depicts another entity.
-
E.
producerOfNotableCoverAlbum
Indicates that an entity produced a cover album that is considered notable or significant.
- F. None of above.
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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836a569d881908b37895c98357429 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.