Triple
T28692712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Abrittus |
E729328
|
entity |
| Predicate | commandedBySideRomanEmpire |
P48696
|
FINISHED |
| Object | Decius |
—
|
NE NERFINISHED |
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: Decius | Statement: [Battle of Abrittus, commandedBySideRomanEmpire, Decius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedBySideRomanEmpire Context triple: [Battle of Abrittus, commandedBySideRomanEmpire, Decius]
-
A.
RomanCommander
chosen
Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
-
B.
ByzantineEmperorInCommand
Indicates that a person holds and exercises the supreme ruling and military authority as the Byzantine emperor.
-
C.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
D.
underRomanEmperor
Indicates that one entity existed, occurred, or was governed during the reign of the specified Roman emperor.
-
E.
ByzantineCommander
Indicates a relationship where an entity holds the role or function of a commander within a Byzantine military or organizational context.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 5:37 a.m.