Triple
T28662787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Antony’s funeral oration |
E725510
|
entity |
| Predicate | keyDevice |
P165188
|
FINISHED |
| Object | verbal irony |
—
|
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: verbal irony | Statement: [Mark Antony’s funeral oration, keyDevice, verbal irony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyDevice Context triple: [Mark Antony’s funeral oration, keyDevice, verbal irony]
-
A.
keyProvision
Indicates that one entity serves as a primary or essential provision, resource, or supply for another entity.
-
B.
keyApplication
Indicates that an application or software program serves as the primary or central tool used for a particular purpose or function.
-
C.
keyHub
Indicates a central or primary element that connects, coordinates, or controls multiple related components or interactions.
-
D.
keyCenter
Indicates the central or primary tonal focus around which other related elements are organized or interpreted.
-
E.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 4:59 a.m.