Triple
T34336597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praying |
E881162
|
entity |
| Predicate | isComebackWorkFor |
P47258
|
FINISHED |
| Object | Kesha |
—
|
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: Kesha | Statement: [Praying, isComebackWorkFor, Kesha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isComebackWorkFor Context triple: [Praying, isComebackWorkFor, Kesha]
-
A.
isComebackCollaborationFor
Indicates that a collaboration serves as a comeback or return project for the associated entity.
-
B.
comebackWorkFor
Indicates that an entity returns to a previous workplace or employer to work again.
-
C.
isComebackEraWorkOf
chosen
Indicates that a work belongs to or represents an artist’s comeback era following a period of reduced activity or absence.
-
D.
madeComeback
Indicates that an entity returned to a previous level of success, performance, or prominence after a period of decline, absence, or setback.
-
E.
respondsToWork
Indicates that one entity replies or reacts to another entity’s work, output, or contribution.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:58 a.m.