Triple
T34507144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boerebista |
E885918
|
entity |
| Predicate | deathCoincidesWith |
P3824
|
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: [Boerebista, deathCoincidesWith, assassination of Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathCoincidesWith Context triple: [Boerebista, deathCoincidesWith, assassination of Julius Caesar]
-
A.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
B.
collisionDate
Indicates the date on which a collision event between entities occurred.
-
C.
reburialCoincidesWith
Indicates that the act of reburial occurs at the same time or within the same event or phase as another specified occurrence.
-
D.
coexistedWith
Indicates that two entities existed at the same time and in the same context or environment, without implying any specific type of interaction between them.
-
E.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 2:01 a.m.