Triple
T13876502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junii Silani |
E333596
|
entity |
| Predicate | cognomen |
P6662
|
FINISHED |
| Object | Silanus |
E710725
|
NE 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: Silanus | Statement: [Junii Silani, cognomen, Silanus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Silanus Context triple: [Junii Silani, cognomen, Silanus]
-
A.
Silanus
chosen
Silanus was a cognomen used by several members of the ancient Roman Julii family, notably borne by politicians and nobles of the late Republic and early Empire.
-
B.
Didius
Didius was the family name of the Roman emperor Didius Julianus, associated with a senatorial lineage in ancient Rome.
-
C.
Flaccus
Flaccus is the cognomen of the Roman poet Quintus Horatius Flaccus, commonly known in English as Horace.
-
D.
Aelius
Aelius is an ancient Roman family name (nomen) associated with several notable figures of the Roman Empire, including emperors and high-ranking officials.
-
E.
Thascius
Thascius is the family name of the early Christian bishop and martyr Cyprian of Carthage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0be556708190bbcf0b3583f677e3 |
completed | April 14, 2026, 9:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c10bb92c8190bd5ab9a5e1d7fabe |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:15 p.m.