Triple
T29715534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Bowness |
E751896
|
entity |
| Predicate | recordLabelFounderOf |
P7869
|
FINISHED |
| Object | Burning Shed |
—
|
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: Burning Shed | Statement: [Tim Bowness, recordLabelFounderOf, Burning Shed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLabelFounderOf Context triple: [Tim Bowness, recordLabelFounderOf, Burning Shed]
-
A.
recordLabelFounded
chosen
Indicates that a particular record label was established or created by a specific founder or founding entity.
-
B.
recordLabelHeadquartersOf
Indicates that a particular location serves as the main headquarters of a specific record label.
-
C.
recordLabelTypeFounded
Indicates that a particular type or category of record label was established or came into existence on a specific date or in a specific time period.
-
D.
recordLabelArtist
Indicates that a musical artist is signed to, represented by, or releases recordings through a particular record label.
-
E.
recordedForLabelFoundedBy
Indicates that an entity (such as an artist or band) recorded for a record label that was founded by a specified person or entity.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 7:33 p.m.