Triple
T8965851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan Brown |
E214129
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Bloom |
E435874
|
NE 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: Bloom | Statement: [Bryan Brown, notableWork, Bloom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bloom Context triple: [Bryan Brown, notableWork, Bloom]
-
A.
Bloom
Bloom is a common English and Jewish surname borne by numerous notable figures in literature, academia, and the arts.
-
B.
Bloom
chosen
Bloom is a large open-access multilingual language model developed by the BigScience research workshop for text generation and understanding tasks.
-
C.
Bloom Innocent
Bloom Innocent is a 2019 studio album by British singer-songwriter and producer Fink, blending atmospheric folk, blues, and electronic influences.
-
D.
In Bloom
"In Bloom" is a popular grunge song by Nirvana, known for its heavy guitar riffs and critique of mainstream misinterpretation of the band's music.
-
E.
Bloomy
Bloomy is an informal nickname commonly used to refer to the city of Bloomington, Indiana.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67623818819096aee155a9b43e8f |
completed | April 1, 2026, 12:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc95514408190ad442069daec0459 |
completed | April 3, 2026, 2:06 p.m. |
Created at: March 30, 2026, 7:01 p.m.