Triple
T23997711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lip Lock |
E594150
|
entity |
| Predicate | followsAfterHiatus |
P103932
|
FINISHED |
| Object | Eve-Olution |
—
|
NE NERFINISHED |
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: Eve-Olution | Statement: [Lip Lock, followsAfterHiatus, Eve-Olution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsAfterHiatus Context triple: [Lip Lock, followsAfterHiatus, Eve-Olution]
-
A.
releasedAfterHiatusOf
Indicates that one entity (typically a work or product) was released following a preceding break or hiatus of the other entity (such as an artist, series, or organization).
-
B.
previousWorkAfterHiatusOf
chosen
Indicates that one work directly follows and resumes activity after a hiatus or break from a previous work.
-
C.
resumesAfter
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
D.
releasedFollowing
Indicates that one entity was released after another entity, in a subsequent or later release order.
-
E.
resumedIn
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d39066f8819096d13bfdd0a047fc |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:38 p.m.