Triple
T2637485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avidius Cassius |
E59780
|
entity |
| Predicate | endCauseOfRevolt |
P42406
|
FINISHED |
| Object | news that Marcus Aurelius was still alive |
—
|
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: news that Marcus Aurelius was still alive | Statement: [Avidius Cassius, endCauseOfRevolt, news that Marcus Aurelius was still alive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endCauseOfRevolt Context triple: [Avidius Cassius, endCauseOfRevolt, news that Marcus Aurelius was still alive]
-
A.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
-
B.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
notableRevolt
Indicates a significant uprising or rebellion in which the subject played an important or historically notable role.
-
D.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
E.
reasonForSecession
Indicates the underlying cause or motivation that led an entity to break away or formally secede from a larger group, organization, or political body.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8e3190081908ea828fe79569cc9 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:50 p.m.