Triple
T9404068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valery |
E226539
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Valerius |
E765169
|
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: Valerius | Statement: [Valery, relatedName, Valerius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Valerius Context triple: [Valery, relatedName, Valerius]
-
A.
Valerius
chosen
Valerius is the Roman family name (nomen) of the poet Gaius Valerius Catullus, indicating his membership in the ancient gens Valeria.
-
B.
Lutatius
Lutatius was an ancient Roman family (gens) whose members, including Quintus Lutatius Catulus, held prominent political and military roles in the Roman Republic.
-
C.
Thascius
Thascius is the family name of the early Christian bishop and martyr Cyprian of Carthage.
-
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.
Caecilius
Caecilius is the family name of a prominent ancient Roman gens that included influential politicians and military leaders such as Quintus Caecilius Metellus Numidicus.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51bf7e5c8190850b671778496150 |
completed | April 1, 2026, 5:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18208ba9081909efa44f98f90c11a |
completed | April 4, 2026, 9:26 p.m. |
Created at: March 30, 2026, 7:46 p.m.