Triple
T29169388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boo’d Up |
E739410
|
entity |
| Predicate | breakoutStatus |
P37426
|
FINISHED |
| Object | breakout R&B hit |
—
|
LITERAL 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: breakout R&B hit | Statement: [Boo’d Up, breakoutStatus, breakout R&B hit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakoutStatus Context triple: [Boo’d Up, breakoutStatus, breakout R&B hit]
-
A.
isBreakoutSingleOf
Indicates that a single is recognized as the breakout or first major hit release for an artist or group.
-
B.
BrockStatus
Indicates the current state or condition associated with Brock in relation to the relevant context or system.
-
C.
hasBreakoutRoleFor
Indicates that an entity serves as the breakout or career-defining role for a particular person or performer.
-
D.
becameBreakoutHitFor
chosen
Indicates that something achieved sudden, widespread popularity or success specifically in relation to a particular entity (such as an artist, brand, or market).
-
E.
BostonBreakersStatus
Indicates the current competitive or organizational state of the Boston Breakers (e.g., active, folded, in-season, off-season) within their league or sport context.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d7fea0819084e702773edd2bfa |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:51 a.m.