Triple
T14014873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unforgettable |
E337177
|
entity |
| Predicate | hasBreakoutSuccess |
P83536
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Unforgettable, hasBreakoutSuccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreakoutSuccess Context triple: [Unforgettable, hasBreakoutSuccess, true]
-
A.
hasBreakoutRoleFor
Indicates that an entity serves as the breakout or career-defining role for a particular person or performer.
-
B.
isBreakoutSingleOf
Indicates that a single is recognized as the breakout or first major hit release for an artist or group.
-
C.
canBreakOutTo
Indicates that one entity has the ability or permission to escape or exit from the context, boundary, or containment defined by another entity.
-
D.
hasNotableSuccessIn
chosen
Indicates that an entity has achieved significant or widely recognized success in a particular field, activity, or domain.
-
E.
hasMaximumBreaks
Indicates that there is an upper limit on the number of breaks allowed or assigned in a given 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f396b648190927e5718c3bb6511 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.