Triple
T31490690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulpia Severina |
E803395
|
entity |
| Predicate | coinageIssuedUnder |
P171694
|
FINISHED |
| Object | Aurelian |
—
|
NE NERFINISHED |
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: Aurelian | Statement: [Ulpia Severina, coinageIssuedUnder, Aurelian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageIssuedUnder Context triple: [Ulpia Severina, coinageIssuedUnder, Aurelian]
-
A.
coinageFeature
Indicates a characteristic, design element, or attribute that is present on or associated with a particular coin or type of coinage.
-
B.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
C.
coinageAttributedTo
Indicates that the creation or origination of a particular coinage (such as a term, phrase, or monetary unit) is attributed to a specific agent or source.
-
D.
coinageContext
Indicates the historical, cultural, or situational circumstances under which something (typically a term, phrase, or currency) was first created or came into use.
-
E.
coinageDate
Indicates the date or time period when a coin (or currency unit) was first minted or officially issued.
- F. None of above. chosen
Provenance (4 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e4ca4881908146cb7b170209d6 |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 30, 2026, 9:38 p.m.