Triple
T22870364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ausonius |
E567174
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Decimus |
—
|
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: Decimus | Statement: [Ausonius, givenName, Decimus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Decimus Context triple: [Ausonius, givenName, Decimus]
-
A.
Decimus
chosen
Decimus is a masculine given name of Latin origin meaning "tenth," historically used in ancient Rome and later borne by various notable figures.
-
B.
Quintus
Quintus is a traditional Latin praenomen (given name) commonly used in ancient Rome, often indicating the fifth-born child or associated with the number five.
-
C.
Aelius
Aelius is an ancient Roman family name (nomen) associated with several notable figures of the Roman Empire, including emperors and high-ranking officials.
-
D.
Messius Quintus
Messius Quintus is an ancient Roman family name associated with the gens Messia, to which the individual Decius belonged.
-
E.
Quintianus
Quintianus is a Roman cognomen derived from the praenomen Quintus, typically indicating familial or ancestral association with someone bearing that name.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f04b06481909004818ec8fc5a26 |
completed | April 29, 2026, 3:46 a.m. |
Created at: April 17, 2026, 3:38 p.m.