Triple
T11641869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Scythian Kingdoms |
E276678
|
entity |
| Predicate | coinageInfluence |
P99871
|
FINISHED |
| Object | Hellenistic coinage |
—
|
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: Hellenistic coinage | Statement: [Indo-Scythian Kingdoms, coinageInfluence, Hellenistic coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageInfluence Context triple: [Indo-Scythian Kingdoms, coinageInfluence, Hellenistic coinage]
-
A.
coinageFeature
chosen
Indicates a characteristic, design element, or attribute that is present on or associated with a particular coin or type of coinage.
-
B.
coinagePower
Indicates the authority or capacity of an entity to create, issue, or regulate currency or coinage.
-
C.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
D.
coinageMotivation
Indicates the reason or purpose motivating the creation or introduction of a particular coinage or monetary issue.
-
E.
coinageDate
Indicates the date or time period when a coin (or currency unit) was first minted or officially issued.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.