Triple
T8950112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Aemilius Scaurus |
E213322
|
entity |
| Predicate | held the office of consul in |
P32960
|
FINISHED |
| Object | 115 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: 115 BC | Statement: [Marcus Aemilius Scaurus, held the office of consul in, 115 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: held the office of consul in Context triple: [Marcus Aemilius Scaurus, held the office of consul in, 115 BC]
-
A.
heldPoliticalOfficeIn
Indicates that an entity served in a political office or position within a specified governmental body or jurisdiction.
-
B.
succeededInOffice
Indicates that one officeholder directly followed another in holding the same official position.
-
C.
servedInOfficeTo
Indicates that one entity held and performed the duties of a particular office or position for the benefit or under the authority of another entity.
-
D.
consulship
chosen
Indicates the relationship in which an individual holds or exercises the office and powers of a consul.
-
E.
memberHeldOfficeFrom
Indicates that a member began holding a particular office or position starting from a specified date or time.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670b5f50819080f1c73992fe5281 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.