Triple
T5460490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Persian cuneiform |
E122581
|
entity |
| Predicate | coOccurringScripts |
P25756
|
FINISHED |
| Object | Elamite 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: Elamite cuneiform | Statement: [Old Persian cuneiform, coOccurringScripts, Elamite cuneiform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coOccurringScripts Context triple: [Old Persian cuneiform, coOccurringScripts, Elamite cuneiform]
-
A.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
B.
appearsInScriptType
Indicates that an entity is featured or occurs within a script of a specified type or category.
-
C.
relatedToScript
Indicates a general association or connection between an entity and a script, without specifying the exact nature of that relationship.
-
D.
appearsAlongside
chosen
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
E.
coexistsWithLanguage
Indicates that one entity exists or functions alongside a particular language at the same time, without excluding or replacing it.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.