Triple
T28824798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Calpurnius Piso Caesoninus |
E727871
|
entity |
| Predicate | consulWith |
P32433
|
FINISHED |
| Object | Aulus Gabinius |
—
|
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: Aulus Gabinius | Statement: [Lucius Calpurnius Piso Caesoninus, consulWith, Aulus Gabinius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consulWith Context triple: [Lucius Calpurnius Piso Caesoninus, consulWith, Aulus Gabinius]
-
A.
coConsulWith
chosen
Indicates that two individuals simultaneously held the office of consul together during the same term or period.
-
B.
consulType
Indicates the specific category or classification of a consular role or office associated with an entity.
-
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.
consulYear
Indicates the year during which a person held the office of consul.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659383cb4819089c7d29821ae8430 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:35 a.m.