Triple
T31916778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Scribonius Libo (consul 34 BC) |
E814853
|
entity |
| Predicate | consul colleague |
P32433
|
FINISHED |
| Object | Mark Antony |
—
|
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: Mark Antony | Statement: [Lucius Scribonius Libo (consul 34 BC), consul colleague, Mark Antony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consul colleague Context triple: [Lucius Scribonius Libo (consul 34 BC), consul colleague, Mark Antony]
-
A.
coConsulWith
chosen
Indicates that two individuals simultaneously held the office of consul together during the same term or period.
-
B.
consularColleague
Indicates that two individuals work together as colleagues within a consulate or consular service.
-
C.
thirdConsul
Indicates that an entity holds the position or role of the third consul in a specified governing body or context.
-
D.
cabinetColleague
Indicates that two individuals serve together as colleagues within the same governing cabinet.
-
E.
formerColleagueOf
Indicates that two entities once worked together as colleagues in the past but no longer do so.
- 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_69f6b1ef9a84819092952e451b98987b |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:02 a.m.