Triple
T32728274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood Loss |
E836876
|
entity |
| Predicate | performerSideProjectOf |
P138779
|
FINISHED |
| Object | Brian Fallon |
—
|
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: Brian Fallon | Statement: [Blood Loss, performerSideProjectOf, Brian Fallon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerSideProjectOf Context triple: [Blood Loss, performerSideProjectOf, Brian Fallon]
-
A.
recordingArtistSideProjectOf
chosen
Indicates that a musical side project is created or led by a particular primary recording artist or band.
-
B.
associatedWithArtistProject
Indicates a relationship where an entity is linked or connected to an artist’s project, such as being involved in, contributing to, or otherwise related to that project.
-
C.
performerNotableWork
Indicates that a performer is significantly associated with or best known for a particular work (such as a performance, production, or recording).
-
D.
worksWithArtist
Indicates that one entity collaborates or engages in professional work with an artist.
-
E.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 1:11 a.m.