Triple
T11195837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flaccus |
E264918
|
entity |
| Predicate | belongsToNamingConvention |
P78011
|
FINISHED |
| Object | Roman naming conventions |
—
|
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 naming conventions | Statement: [Flaccus, belongsToNamingConvention, Roman naming conventions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNamingConvention Context triple: [Flaccus, belongsToNamingConvention, Roman naming conventions]
-
A.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
belongsToNamingTradition
chosen
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
C.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
D.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
E.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8bf14e481908563b15790af4d20 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.