Triple
T12629723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Asinius Gallus Saloninus |
E301607
|
entity |
| Predicate | consulType |
P106103
|
FINISHED |
| Object | ordinary consul |
—
|
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: ordinary consul | Statement: [Gaius Asinius Gallus Saloninus, consulType, ordinary consul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consulType Context triple: [Gaius Asinius Gallus Saloninus, consulType, ordinary consul]
-
A.
coConsulWith
Indicates that two individuals simultaneously held the office of consul together during the same term or period.
-
B.
secondConsul
Indicates that an individual holds the position of the second consul in a consular pair or sequence.
-
C.
thirdConsul
Indicates that an entity holds the position or role of the third consul in a specified governing body or context.
-
D.
typeOfCluster
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
E.
controlPlaneType
Indicates the type or mode of control plane used to manage and coordinate the system’s components or network operations.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:15 p.m.