Triple
T28662810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Antony’s funeral oration |
E725510
|
entity |
| Predicate | relatedHistoricalEvent |
P115640
|
FINISHED |
| Object | historical funeral of Julius Caesar |
—
|
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: historical funeral of Julius Caesar | Statement: [Mark Antony’s funeral oration, relatedHistoricalEvent, historical funeral of Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedHistoricalEvent Context triple: [Mark Antony’s funeral oration, relatedHistoricalEvent, historical funeral of Julius Caesar]
-
A.
historicalEventDescribedAs
Indicates that a historical event is characterized or portrayed using a particular description, label, or narrative.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
historicalEventsDescribed
chosen
Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
-
D.
associatedEpicEvent
Indicates that one entity is linked or connected to a particular epic event in a relevant or meaningful way.
-
E.
historicEventAlsoKnownAs
Indicates that a historic event is referred to by an alternative name or alias.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: April 28, 2026, 4:59 a.m.