Triple
T22518930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frataraka rulers |
E556721
|
entity |
| Predicate | coinageFeatures |
P99871
|
FINISHED |
| Object | Zoroastrian fire altar |
—
|
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: Zoroastrian fire altar | Statement: [Frataraka rulers, coinageFeatures, Zoroastrian fire altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageFeatures Context triple: [Frataraka rulers, coinageFeatures, Zoroastrian fire altar]
-
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.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
C.
coinCharacteristic
Indicates that a coin possesses a particular attribute, feature, or quality.
-
D.
coinagePower
Indicates the authority or capacity of an entity to create, issue, or regulate currency or coinage.
-
E.
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.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e30a96081909b8511d525518da1 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.