Triple
T8618750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintus Caecilius Metellus Numidicus |
E204107
|
entity |
| Predicate | heldConsulshipInYear |
P32050
|
FINISHED |
| Object | 109 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: 109 BC | Statement: [Quintus Caecilius Metellus Numidicus, heldConsulshipInYear, 109 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldConsulshipInYear Context triple: [Quintus Caecilius Metellus Numidicus, heldConsulshipInYear, 109 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.
numberOfConsulships
Indicates the total count of times an entity has held the office or role of consul.
-
D.
firstConsulshipYear
Indicates the calendar year in which an entity held its first consulship or began serving its first term as consul.
-
E.
consulYear
chosen
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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4712e74c81908b607a0ab2f9a361 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.