Triple
T14714679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aemilius |
E345645
|
entity |
| Predicate | belongsToOnomasticSystem |
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: [Aemilius, belongsToOnomasticSystem, Roman naming conventions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOnomasticSystem Context triple: [Aemilius, belongsToOnomasticSystem, Roman naming conventions]
-
A.
belongsToNamingTradition
chosen
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
B.
hasNounSystemFrom
Indicates that something possesses or is associated with a noun-based system that originates from or is derived from a specified source.
-
C.
hasOnomasticField
Indicates a relationship where something is associated with a specific onomastic field, i.e., a domain or category related to names or naming conventions.
-
D.
belongsToSystemType
Indicates that one entity is classified under, or is a member of, a particular system type.
-
E.
belongsToAdministrativeSystem
Indicates that one entity is part of, or under the jurisdiction of, a particular administrative system or framework.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98513b081908b230f6ac79c72ad |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.