Triple
T3625869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carinus |
E76836
|
entity |
| Predicate | notableBattleOutcome |
P19109
|
FINISHED |
| Object | defeated by Diocletian at the Margus |
—
|
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: defeated by Diocletian at the Margus | Statement: [Carinus, notableBattleOutcome, defeated by Diocletian at the Margus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBattleOutcome Context triple: [Carinus, notableBattleOutcome, defeated by Diocletian at the Margus]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
notableBattleDuringReign
Indicates that a particular battle is notably associated with and occurred during the time span of a specific ruler’s reign.
-
C.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
D.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
E.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2dae7a48190809d4455b2349aaa |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.