Triple
T28502784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Octavius (consul 75 BC) |
E721279
|
entity |
| Predicate | nomenGentilicium |
P141718
|
FINISHED |
| Object | Octavius |
—
|
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: Octavius | Statement: [Lucius Octavius (consul 75 BC), nomenGentilicium, Octavius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nomenGentilicium Context triple: [Lucius Octavius (consul 75 BC), nomenGentilicium, Octavius]
-
A.
gentilicium
chosen
Indicates that an entity’s family or clan affiliation is expressed through a gentilic (family) name.
-
B.
usesGentilicFor
Indicates that one entity refers to another using a gentilic (a demonym or term denoting origin, nationality, or regional affiliation).
-
C.
onomasticType
Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
-
D.
praenomenOrNomen
Indicates that the related name element functions either as a personal given name (praenomen) or as a family/clan name (nomen) within a naming system.
-
E.
partOfOnomasticsCategory
Indicates that one concept or term belongs to, or is classified under, a specific category within the field of onomastics (the study of names).
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f44f82881909737e28390ab5e4a |
completed | May 2, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:07 a.m.