Triple
T30193862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Publius Cornelius Scipio (consul 16 BC) |
E767568
|
entity |
| Predicate | consulOf |
P32960
|
FINISHED |
| Object | Roman Empire |
—
|
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: Roman Empire | Statement: [Publius Cornelius Scipio (consul 16 BC), consulOf, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consulOf Context triple: [Publius Cornelius Scipio (consul 16 BC), consulOf, Roman Empire]
-
A.
consulship
chosen
Indicates the relationship in which an individual holds or exercises the office and powers of a consul.
-
B.
thirdConsul
Indicates that an entity holds the position or role of the third consul in a specified governing body or context.
-
C.
coConsulWith
Indicates that two individuals simultaneously held the office of consul together during the same term or period.
-
D.
secondConsul
Indicates that an individual holds the position of the second consul in a consular pair or sequence.
-
E.
consulYear
Indicates the year during which a person held the office of consul.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f86218c8190918d9a725306fb43 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:29 p.m.