Triple
T28687998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Antonius |
E729189
|
entity |
| Predicate | positionHeldAsConsulWith |
P169730
|
FINISHED |
| Object | Publius Servilius Vatia Isauricus |
—
|
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: Publius Servilius Vatia Isauricus | Statement: [Lucius Antonius, positionHeldAsConsulWith, Publius Servilius Vatia Isauricus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHeldAsConsulWith Context triple: [Lucius Antonius, positionHeldAsConsulWith, Publius Servilius Vatia Isauricus]
-
A.
consulshipWith
chosen
Indicates a relationship where two or more entities jointly hold, share, or are associated with the same consulship or consular office.
-
B.
numberOfConsulships
Indicates the total count of times an entity has held the office or role of consul.
-
C.
consulship
Indicates the relationship in which an individual holds or exercises the office and powers of a consul.
-
D.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
E.
precededInConsulshipBy
Indicates that one consul’s term of office occurred immediately before another consul’s term.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 28, 2026, 5:34 a.m.