Triple
T29809319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bright Red |
E756913
|
entity |
| Predicate | performerOnWork |
P57842
|
FINISHED |
| Object | Brian Eno |
—
|
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 Eno | Statement: [Bright Red, performerOnWork, Brian Eno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerOnWork Context triple: [Bright Red, performerOnWork, Brian Eno]
-
A.
performerOn
chosen
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
B.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
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.
performedInWorkBy
Indicates that an action or role was carried out within a specific work (e.g., a film, book, or composition) by a particular agent or contributor.
-
E.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 5:22 p.m.