Triple
T30465507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Raudine Plain |
E775125
|
entity |
| Predicate | MariusConsulshipNumber |
P169468
|
FINISHED |
| Object | fifth consulship of Gaius Marius |
—
|
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: fifth consulship of Gaius Marius | Statement: [Battle of the Raudine Plain, MariusConsulshipNumber, fifth consulship of Gaius Marius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MariusConsulshipNumber Context triple: [Battle of the Raudine Plain, MariusConsulshipNumber, fifth consulship of Gaius Marius]
-
A.
firstConsulshipYear
Indicates the calendar year in which an entity held its first consulship or began serving its first term as consul.
-
B.
consulshipYear
Indicates the specific year during which an entity held or is associated with a consulship office or term.
-
C.
precededInConsulshipBy
Indicates that one consul’s term of office occurred immediately before another consul’s term.
-
D.
praetorshipYear
Indicates the specific year in which an entity held or exercised the office or role of praetor.
-
E.
tribunateYear
Indicates the year in which a person held or exercised the office of tribune.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f314fc81908a65eec389e8b1fb |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:11 p.m.