Triple
T31916897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Scribonius Libo (consul 16 AD) |
E814856
|
entity |
| Predicate | consul during reign of |
P169365
|
FINISHED |
| Object | Tiberius |
—
|
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: Tiberius | Statement: [Lucius Scribonius Libo (consul 16 AD), consul during reign of, Tiberius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consul during reign of Context triple: [Lucius Scribonius Libo (consul 16 AD), consul during reign of, Tiberius]
-
A.
consulDuringReignOf
chosen
Indicates that a person held the office of consul during the reign of a specified ruler or sovereign.
-
B.
consulship
Indicates the relationship in which an individual holds or exercises the office and powers of a consul.
-
C.
concludedDuringReignOf
Indicates that an event, process, or state came to an end while a particular ruler’s reign or period of authority was ongoing.
-
D.
modifiedDuringReignOf
Indicates that an entity was altered, updated, or changed while a particular ruler or authority was in power.
-
E.
consulshipWith
Indicates a relationship where two or more entities jointly hold, share, or are associated with the same consulship or consular office.
- 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_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:02 a.m.