Triple
T31391876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Dig Love |
E800751
|
entity |
| Predicate | isFromSoloCareerOf |
P137604
|
FINISHED |
| Object | George Harrison |
—
|
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: George Harrison | Statement: [I Dig Love, isFromSoloCareerOf, George Harrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromSoloCareerOf Context triple: [I Dig Love, isFromSoloCareerOf, George Harrison]
-
A.
hasSoloCareer
Indicates that an individual has pursued a musical or artistic career independently, separate from any group or band affiliations.
-
B.
isFromArtistSoloCareer
chosen
Indicates that the work or contribution originates from an artist’s solo career rather than from a group or band they are associated with.
-
C.
isSoloDebutOf
Indicates that an event, work, or performance is the first solo appearance or release of a particular individual.
-
D.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
E.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
- 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_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.