Triple
T13285735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gens Domitia |
E316438
|
entity |
| Predicate | usedNamingConvention |
P1217
|
FINISHED |
| Object | Roman tria nomina system |
—
|
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: Roman tria nomina system | Statement: [gens Domitia, usedNamingConvention, Roman tria nomina system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedNamingConvention Context triple: [gens Domitia, usedNamingConvention, Roman tria nomina system]
-
A.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
usesNamingSystem
chosen
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
C.
usedConstructorName
Indicates that a particular constructor was invoked using a specific constructor name in the creation or initialization of an entity.
-
D.
logicConvention
Indicates a relationship where entities participate in or are associated with a convention, event, or standard related to logic or logical systems.
-
E.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.