Triple
T11028512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Still Hurting |
E260694
|
entity |
| Predicate | chronologicalPlacementInStory |
P59803
|
FINISHED |
| Object | after the breakup |
—
|
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: after the breakup | Statement: [Still Hurting, chronologicalPlacementInStory, after the breakup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPlacementInStory Context triple: [Still Hurting, chronologicalPlacementInStory, after the breakup]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
chronologicalOrderInSeries
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
-
C.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
D.
narrativeSequence
chosen
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
-
E.
chronologicallyFocusesOn
Indicates that something is primarily concerned with or organized around the sequence and progression of events over time.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797d245a0819085135cdee9b256c5 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.