Triple
T29635385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dobunni |
E755697
|
entity |
| Predicate | coinageStyle |
P99871
|
FINISHED |
| Object | inscribed coins |
—
|
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: inscribed coins | Statement: [Dobunni, coinageStyle, inscribed coins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageStyle Context triple: [Dobunni, coinageStyle, inscribed coins]
-
A.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
B.
coinageFeature
chosen
Indicates a characteristic, design element, or attribute that is present on or associated with a particular coin or type of coinage.
-
C.
laterCoinageStyle
Indicates that one entity’s style or design is modeled after, influenced by, or characteristic of a later period of coinage relative to another.
-
D.
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.
-
E.
coinedDesign
Indicates that an entity originated or created a particular design or stylistic concept.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66e6a2790819082fb230e553bf4c5 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:43 p.m.