Triple
T8362483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesonia |
E197041
|
entity |
| Predicate | belongsToOnomasticTradition |
P45665
|
FINISHED |
| Object | Roman onomastics |
—
|
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 onomastics | Statement: [Caesonia, belongsToOnomasticTradition, Roman onomastics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOnomasticTradition Context triple: [Caesonia, belongsToOnomasticTradition, Roman onomastics]
-
A.
belongsToNamingTradition
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
B.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
C.
partOfOnomasticTradition
chosen
Indicates that something belongs to, or is included within, a particular onomastic (name-giving) tradition.
-
D.
countryOfNamingTradition
Indicates the country whose cultural or linguistic naming conventions are used to form or interpret a given name.
-
E.
onTraditionalCountryOf
Indicates that something is located within or associated with the traditional country or ancestral lands of a particular group.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8074e4588190b394d1622adca2cb |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.