Triple
T16774333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linear Elamite |
E407682
|
entity |
| Predicate | hasUndecipheredStatus |
P11828
|
FINISHED |
| Object | partially deciphered |
—
|
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: partially deciphered | Statement: [Linear Elamite, hasUndecipheredStatus, partially deciphered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndecipheredStatus Context triple: [Linear Elamite, hasUndecipheredStatus, partially deciphered]
-
A.
isUndeciphered
Indicates that something has not yet been successfully interpreted, decoded, or understood in terms of its meaning or structure.
-
B.
deciphermentStatus
chosen
Indicates the degree to which something (such as a text, code, or inscription) has been successfully decoded or interpreted.
-
C.
hasSignatureStatusFor
Indicates that a specific entity holds or is assigned a particular signature-related status in relation to another entity or context.
-
D.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
E.
hasDisputedStatus
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b038d0608190be15c758427bb664 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.