Triple
T31916926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Scribonius Libo (consul 16 AD) |
E814856
|
entity |
| Predicate | preceded by (as consul) |
P113233
|
FINISHED |
| Object | consuls of 15 AD |
—
|
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: consuls of 15 AD | Statement: [Lucius Scribonius Libo (consul 16 AD), preceded by (as consul), consuls of 15 AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preceded by (as consul) Context triple: [Lucius Scribonius Libo (consul 16 AD), preceded by (as consul), consuls of 15 AD]
-
A.
precededInConsulshipBy
chosen
Indicates that one consul’s term of office occurred immediately before another consul’s term.
-
B.
succeededInConsulshipBy
Indicates that one individual’s term in the consulship was immediately followed by another individual’s term in the same office.
-
C.
precededBy (as Prime Minister)
Indicates that one person previously held the office of Prime Minister before another person.
-
D.
precededGovernment
Indicates that one government directly came before another in a temporal or historical sequence.
-
E.
precededByAsRegent
Indicates that one entity previously served as regent before another entity, in a directly preceding position of regency.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:02 a.m.