Triple
T24980322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Monkey Don't Stop No Show |
E625143
|
entity |
| Predicate | afterDepartureOf |
P140407
|
FINISHED |
| Object | CeeLo Green |
—
|
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: CeeLo Green | Statement: [One Monkey Don't Stop No Show, afterDepartureOf, CeeLo Green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterDepartureOf Context triple: [One Monkey Don't Stop No Show, afterDepartureOf, CeeLo Green]
-
A.
followsDepartureOf
Indicates that one event or action occurs after and in sequence with the departure of another entity or event.
-
B.
originatedAfterDepartureFrom
chosen
Indicates that one event, state, or entity began or came into existence only after the departure or leaving of another specified entity or event.
-
C.
hasDepartureTo
Indicates that a departure event originates from one place and is directed toward a specific destination.
-
D.
hasCompanionDeparture
Indicates that an entity’s departure is associated with, or accompanied by, the departure of a companion entity.
-
E.
departsFrom
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490531148190825ab7084a2616f3 |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:02 a.m.