Triple
T22465444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Chorasmian |
E555339
|
entity |
| Predicate | usesAramaicIdeograms |
P32395
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Old Chorasmian, usesAramaicIdeograms, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAramaicIdeograms Context triple: [Old Chorasmian, usesAramaicIdeograms, true]
-
A.
usesLogogramsFrom
chosen
Indicates that one writing system or notation incorporates or employs logographic characters originating from another system.
-
B.
isOnlySemiticLanguageWrittenIn
Indicates that a language is the sole Semitic language used in a specified writing system or script.
-
C.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
-
D.
nameInAramaic
Indicates that an entity has a specific name expressed in the Aramaic language.
-
E.
usesColloquialCharacters
Indicates that an expression, name, or text is written using informal, non-standard, or colloquial characters rather than formal or standard script.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b837ec081909c4e44d37e8b2acd |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.