Triple
T20360320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Come Away, Come Away, Death |
E496756
|
entity |
| Predicate | belongsToGenreOfWork |
P62560
|
FINISHED |
| Object | comedy (host play) |
—
|
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: comedy (host play) | Statement: [Come Away, Come Away, Death, belongsToGenreOfWork, comedy (host play)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGenreOfWork Context triple: [Come Away, Come Away, Death, belongsToGenreOfWork, comedy (host play)]
-
A.
belongsToWorkGenre
chosen
Indicates that a creative work is classified under or associated with a particular genre.
-
B.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
C.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
D.
genreOfOriginWork
Indicates that a work is classified under a particular genre based on the genre of its original source work.
-
E.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678584294819093788ccf2fb8e588 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.