Triple
T8310557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippicae |
E194578
|
entity |
| Predicate | rhetoricalTechniques |
P834
|
FINISHED |
| Object | invective |
—
|
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: invective | Statement: [Philippicae, rhetoricalTechniques, invective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rhetoricalTechniques Context triple: [Philippicae, rhetoricalTechniques, invective]
-
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.
rhetoricalStyle
Indicates the characteristic manner or technique of expression used in communication, such as tone, structure, and persuasive strategies.
-
C.
hasDramaticTechnique
Indicates that one entity employs, features, or is characterized by a particular dramatic technique associated with another entity.
-
D.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
-
E.
languageOfPropaganda
Indicates that a particular language is used as the medium or vehicle for disseminating propaganda.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2eecb08190ae0ba8adbaf58c8f |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.