Triple
T607071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clouds |
E12016
|
entity |
| Predicate | literaryDevice |
P834
|
FINISHED |
| Object | parody |
—
|
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: parody | Statement: [Clouds, literaryDevice, parody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryDevice Context triple: [Clouds, literaryDevice, parody]
-
A.
rhetoricalDevice
chosen
Indicates that one entity is used as a rhetorical device in relation to another, such as a figure of speech, stylistic technique, or persuasive strategy within a discourse.
-
B.
literaryLanguage
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
C.
literaryMovement
Indicates the artistic or intellectual movement in literature with which a work, author, or text is associated or to which it belongs.
-
D.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
E.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df34abc8190a578c8c2ab3d28e4 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.