Triple
T17311397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diva’s Lament |
E420304
|
entity |
| Predicate | complainsAbout |
P126925
|
FINISHED |
| Object | not having enough stage time |
—
|
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: not having enough stage time | Statement: [Diva’s Lament, complainsAbout, not having enough stage time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complainsAbout Context triple: [Diva’s Lament, complainsAbout, not having enough stage time]
-
A.
complainant
Indicates that an entity is the person or party who makes a complaint or brings a grievance against another entity.
-
B.
handlesComplaintsOn
Indicates that one entity is responsible for receiving, managing, or resolving complaints related to another entity.
-
C.
concernsProblem
Indicates that something is about, related to, or deals with a particular problem or issue.
-
D.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
E.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439993bac8190a72f6af529bd7cce |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.