Triple
T10885276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mursa Major |
E257025
|
entity |
| Predicate | yearInRomanHistory |
P96235
|
FINISHED |
| Object | 351 in the Roman Empire |
—
|
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: 351 in the Roman Empire | Statement: [Battle of Mursa Major, yearInRomanHistory, 351 in the Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearInRomanHistory Context triple: [Battle of Mursa Major, yearInRomanHistory, 351 in the Roman Empire]
-
A.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
B.
yearOfSackOfRome
Indicates the specific year in which the Sack of Rome took place.
-
C.
underRomanRuleBecame
Indicates that an entity, once under Roman political or administrative control, subsequently transformed into or was reconstituted as another specified entity.
-
D.
usedInRomanPeriodFor
Indicates that something served a particular function, purpose, or application during the Roman period.
-
E.
dateInRomanCalendar
Indicates that a given date is expressed according to the conventions and structure of the ancient Roman calendar system.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dd6a3c81909965ef774e8b7309 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.