Triple
T25715872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oraisons funèbres |
E644861
|
entity |
| Predicate | rhetoricalAim |
P159004
|
FINISHED |
| Object | consolation |
—
|
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: consolation | Statement: [Oraisons funèbres, rhetoricalAim, consolation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rhetoricalAim Context triple: [Oraisons funèbres, rhetoricalAim, consolation]
-
A.
rhetoricalAim
chosen
Indicates the intended persuasive or communicative effect that an utterance or text is designed to achieve in its audience.
-
B.
aimsToPersuade
Indicates an intentional effort by one entity to influence or change another entity’s beliefs, attitudes, or decisions.
-
C.
aimOfEnglish
Indicates that something serves as the goal, purpose, or intended outcome within the context of English (e.g., English language, subject, or curriculum).
-
D.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
E.
rhetoricalStyle
Indicates the characteristic manner or technique of expression used in communication, such as tone, structure, and persuasive strategies.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 9:41 p.m.