Triple
T38299285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brave and Crazy |
E1032177
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object |
Never Enough
"Never Enough" is a music album, likely a follow-up release to "Brave and Crazy," known within the discography of the same artist.
|
E2266994
|
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: Never Enough | Statement: [Brave and Crazy, followedBy, Never Enough]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Never Enough Triple: [Brave and Crazy, followedBy, Never Enough]
Generated description
"Never Enough" is a music album, likely a follow-up release to "Brave and Crazy," known within the discography of the same artist.
Provenance (5 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc618ba08819088ced2c3fc1d7b84 |
completed | May 7, 2026, 5:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b28e15788190acceb5d2635dc7a0 |
completed | June 28, 2026, 11:47 p.m. |
| NEDg | Description generation | batch_6a41b2efbe18819084f47a57f2df2cd0 |
completed | June 28, 2026, 11:49 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a41b354160881909a06fbeb7e583e15 |
completed | June 28, 2026, 11:50 p.m. |
Created at: May 3, 2026, 4:30 p.m.