Triple
T16112614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaemenid royal inscriptions |
E390915
|
entity |
| Predicate | deciphermentKeyFor |
P58666
|
FINISHED |
| Object | Old Persian cuneiform |
—
|
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: Old Persian cuneiform | Statement: [Achaemenid royal inscriptions, deciphermentKeyFor, Old Persian cuneiform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deciphermentKeyFor Context triple: [Achaemenid royal inscriptions, deciphermentKeyFor, Old Persian cuneiform]
-
A.
decipheredFrom
Indicates that something has been interpreted, decoded, or understood based on information derived from another source.
-
B.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
-
C.
deciphers
Indicates the action of successfully interpreting or figuring out the meaning of something that is difficult to understand or encoded.
-
D.
cipherKey
chosen
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
E.
deciphermentStatus
Indicates the degree to which something (such as a text, code, or inscription) has been successfully decoded or interpreted.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20167ee1481909e56dc632bfc0fc5 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.