Triple
T31389464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Caudine Forks |
E800690
|
entity |
| Predicate | RomanConsulInvolved |
P39445
|
FINISHED |
| Object | Titus Veturius Calvinus |
—
|
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: Titus Veturius Calvinus | Statement: [Battle of the Caudine Forks, RomanConsulInvolved, Titus Veturius Calvinus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanConsulInvolved Context triple: [Battle of the Caudine Forks, RomanConsulInvolved, Titus Veturius Calvinus]
-
A.
servedAlongsideAsConsul217BC
Indicates that two individuals held the office of consul concurrently in the year 217 BC.
-
B.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
C.
MariusConsulshipNumber
Indicates the ordinal number of a consulship held by Marius in a given term or context.
-
D.
precededInConsulshipBy
Indicates that one consul’s term of office occurred immediately before another consul’s term.
-
E.
roleInRome
chosen
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 9:19 p.m.