Triple
T6529900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Up Out My Face |
E152203
|
entity |
| Predicate | hasBreakupTheme |
P71439
|
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: [Up Out My Face, hasBreakupTheme, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreakupTheme Context triple: [Up Out My Face, hasBreakupTheme, true]
-
A.
breakUpSeason
Indicates the time of year or season during which a romantic relationship ends or a breakup occurs.
-
B.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
C.
plannedBreakupAnnounced
Indicates that a previously intended or scheduled breakup between parties has been publicly or explicitly announced.
-
D.
willLikelyBreakUpIn
Indicates that a romantic relationship between two entities is expected to end within a specified time frame or context.
-
E.
breakupLinkedTo
Indicates a causal or associative relationship where a breakup is connected to, influenced by, or results from another event, factor, or entity.
- F. None of above. chosen
Provenance (4 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adac53b0819097fece48a75cc48f |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:46 p.m.