Triple
T33975526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titus Aebutius Helva |
E871127
|
entity |
| Predicate | servedAsConsulWith |
P32433
|
FINISHED |
| Object | Gaius Veturius Geminus Cicurinus |
—
|
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: Gaius Veturius Geminus Cicurinus | Statement: [Titus Aebutius Helva, servedAsConsulWith, Gaius Veturius Geminus Cicurinus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsConsulWith Context triple: [Titus Aebutius Helva, servedAsConsulWith, Gaius Veturius Geminus Cicurinus]
-
A.
coConsulWith
chosen
Indicates that two individuals simultaneously held the office of consul together during the same term or period.
-
B.
consulshipWith
Indicates a relationship where two or more entities jointly hold, share, or are associated with the same consulship or consular office.
-
C.
thirdConsul
Indicates that an entity holds the position or role of the third consul in a specified governing body or context.
-
D.
secondConsul
Indicates that an individual holds the position of the second consul in a consular pair or sequence.
-
E.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 1:50 a.m.