Triple
T30221088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Aemilius Scaurus |
E768345
|
entity |
| Predicate | officeStartAsConsul |
P73495
|
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, officeStartAsConsul, 115 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartAsConsul Context triple: [Marcus Aemilius Scaurus, officeStartAsConsul, 115 BC]
-
A.
coConsulWith
Indicates that two individuals simultaneously held the office of consul together during the same term or period.
-
B.
secondConsul
Indicates that an individual holds the position of the second consul in a consular pair or sequence.
-
C.
consulType
Indicates the specific category or classification of a consular role or office associated with an entity.
-
D.
thirdConsul
Indicates that an entity holds the position or role of the third consul in a specified governing body or context.
-
E.
officeStartFor
chosen
Indicates the time or date at which an entity begins its term, role, or period of service in an office or official position.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: April 29, 2026, 7:35 p.m.