Triple
T5182148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darius the Mede |
E116945
|
entity |
| Predicate | textualLanguage |
P9828
|
FINISHED |
| Object | Biblical Aramaic |
—
|
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: Biblical Aramaic | Statement: [Darius the Mede, textualLanguage, Biblical Aramaic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualLanguage Context triple: [Darius the Mede, textualLanguage, Biblical Aramaic]
-
A.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
B.
literaryLanguage
chosen
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
C.
contentLanguage
Indicates the language in which the content is expressed or intended to be understood.
-
D.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
-
E.
languageIndependence
Indicates that a concept, method, or representation does not depend on any specific programming or natural language and can be applied uniformly across different languages.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799bc58c819098a8e91e21baaef4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.