Triple
T11511669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huvishka |
E272926
|
entity |
| Predicate | coinageFeature |
P99871
|
FINISHED |
| Object | Greek legends |
—
|
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: Greek legends | Statement: [Huvishka, coinageFeature, Greek legends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageFeature Context triple: [Huvishka, coinageFeature, Greek legends]
-
A.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
B.
coinagePower
Indicates the authority or capacity of an entity to create, issue, or regulate currency or coinage.
-
C.
coinageDate
Indicates the date or time period when a coin (or currency unit) was first minted or officially issued.
-
D.
coinedDenomination
Indicates that an entity created or introduced a particular name, term, or denomination for something.
-
E.
typeOfCoinageReform
Indicates a relationship where a specific reform is classified by the particular type or category of coinage reform it represents.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db7af688190b68668eb39d382a8 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.