Triple
T36515508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbula |
E900026
|
entity |
| Predicate | partOfRomanNamingSystemElement |
P82301
|
FINISHED |
| Object | tria nomina |
—
|
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: tria nomina | Statement: [Barbula, partOfRomanNamingSystemElement, tria nomina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRomanNamingSystemElement Context triple: [Barbula, partOfRomanNamingSystemElement, tria nomina]
-
A.
partOfRomanNamingSystem
chosen
Indicates that something functions as a component or element within the traditional Roman naming system.
-
B.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
C.
royalPrenomen
Indicates the formal throne name adopted by a monarch as part of their royal titulary.
-
D.
isPraenomenOf
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
-
E.
memberHasPraenomen
Indicates that a member is associated with or bears a specific praenomen (personal given name).
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00d9717a9881908194163d719f14d6 |
completed | May 10, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a00d91db2ec81909ebacfc9f0d11dd8 |
completed | May 10, 2026, 7:14 p.m. |
Created at: May 3, 2026, 4:10 p.m.