Triple
T28687999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Antonius |
E729189
|
entity |
| Predicate | startTimeOfConsulship |
P32430
|
FINISHED |
| Object | 41 BC |
—
|
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: 41 BC | Statement: [Lucius Antonius, startTimeOfConsulship, 41 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfConsulship Context triple: [Lucius Antonius, startTimeOfConsulship, 41 BC]
-
A.
consulshipYear
Indicates the specific year during which an entity held or is associated with a consulship office or term.
-
B.
lastConsulshipYear
Indicates the specific year in which an entity most recently held the office of consul.
-
C.
firstConsulshipYear
chosen
Indicates the calendar year in which an entity held its first consulship or began serving its first term as consul.
-
D.
startTimeOfFederationLeadership
Indicates the point in time at which a particular federation leadership role or term begins.
-
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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 28, 2026, 5:34 a.m.