Triple
T9978027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De officiis |
E196380
|
entity |
| Predicate | writtenAfterEvent |
P3117
|
FINISHED |
| Object | assassination 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: assassination of Julius Caesar | Statement: [De officiis, writtenAfterEvent, assassination of Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenAfterEvent Context triple: [De officiis, writtenAfterEvent, assassination of Julius Caesar]
-
A.
writtenAtEvent
Indicates that a writing or inscription activity occurred during or in connection with a specific event.
-
B.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
C.
createdAfterEvent
chosen
Indicates that the creation of one entity occurred after a specified event in time.
-
D.
laterWrittenDownIn
Indicates that information, events, or content were recorded or documented at a later time than when they originally occurred or were created.
-
E.
laterWrittenIn
Indicates that one text or version was written at a later time than another, establishing a chronological order between the writings.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84ef8ac8190abbe78b7611c5309 |
completed | April 2, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.