Triple
T27578493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sour Mash Records |
E699517
|
entity |
| Predicate | founderNotableFor |
P34633
|
FINISHED |
| Object | lead guitarist of Oasis |
—
|
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: lead guitarist of Oasis | Statement: [Sour Mash Records, founderNotableFor, lead guitarist of Oasis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderNotableFor Context triple: [Sour Mash Records, founderNotableFor, lead guitarist of Oasis]
-
A.
founderKnownFor
chosen
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
B.
founderAlsoKnownAs
Indicates that an individual who is a founder of something is also known by an alternative name or alias.
-
C.
founderBirthPlace
Indicates the place where the founder of an entity was born.
-
D.
founderBirthName
Indicates the original personal name given at birth to the individual who founded an organization or entity.
-
E.
wasFoundedBy
Indicates that an organization, institution, or entity came into existence through the initiating action or establishment by a specific founder or founding group.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 2:02 p.m.