Triple
T10480903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyari dialect |
E247164
|
entity |
| Predicate | languageCodeScope |
P68948
|
FINISHED |
| Object | covered under Assyrian Neo‑Aramaic (aii) |
—
|
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: covered under Assyrian Neo‑Aramaic (aii) | Statement: [Tyari dialect, languageCodeScope, covered under Assyrian Neo‑Aramaic (aii)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCodeScope Context triple: [Tyari dialect, languageCodeScope, covered under Assyrian Neo‑Aramaic (aii)]
-
A.
hasLanguageCodeScope
chosen
Indicates that a language code is valid or applicable only within a specified scope, context, or domain.
-
B.
linguisticScope
Indicates the range or domain within language (such as a phrase, clause, or discourse segment) over which a particular linguistic element, feature, or operation has effect.
-
C.
languageCodeRelation
Indicates a relationship where one entity is associated with, identified by, or mapped to a specific language code of another entity.
-
D.
languageCodeISO639-1
Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
-
E.
languageCodeStandard
Indicates that a language code conforms to a specific standardized coding scheme (such as ISO language code standards).
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095c5dc88190902582db28df01b4 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:22 p.m.