Triple
T29084646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Arar |
E734071
|
entity |
| Predicate | RomanLeaderTitle |
P169666
|
FINISHED |
| Object | proconsul of Gaul |
—
|
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: proconsul of Gaul | Statement: [Battle of the Arar, RomanLeaderTitle, proconsul of Gaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanLeaderTitle Context triple: [Battle of the Arar, RomanLeaderTitle, proconsul of Gaul]
-
A.
RomanCommander
Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
-
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.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
D.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
E.
romanCivitasName
Indicates that an entity bears the official Roman civitas (city or community) name associated with it.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 28, 2026, 10:59 a.m.