Triple
T17850724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heliocles II |
E445795
|
entity |
| Predicate | depictedOnCoinReverse |
P129405
|
FINISHED |
| Object | standing deity |
—
|
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: standing deity | Statement: [Heliocles II, depictedOnCoinReverse, standing deity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictedOnCoinReverse Context triple: [Heliocles II, depictedOnCoinReverse, standing deity]
-
A.
obverseDepiction
Indicates that one entity is depicted on the obverse (front) side of another, such as the front face of a coin or medal.
-
B.
obverseOrReverse
Indicates that two sides or aspects of the same object or item are being related as its obverse (front) and reverse (back).
-
C.
obverseDesignIntroduced
Indicates that a particular obverse design (front side of an item, typically a coin or medal) was first put into official use at a specified time.
-
D.
denominationDepicted
Indicates that an item visually represents or shows the monetary denomination (value) of a currency.
-
E.
obverseStyle
Indicates the artistic or design style used on the obverse (front) side of an object, such as a coin or medal.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffe415c8190aed351c52b78a143 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:16 a.m.