Triple
T32133786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khas Arya |
E820717
|
entity |
| Predicate | historicallyAssociatedLanguage |
P141229
|
FINISHED |
| Object | Khas language |
—
|
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: Khas language | Statement: [Khas Arya, historicallyAssociatedLanguage, Khas language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyAssociatedLanguage Context triple: [Khas Arya, historicallyAssociatedLanguage, Khas language]
-
A.
historicalLanguageOfBearers
chosen
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
B.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
C.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
D.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
E.
historicalLanguageOfHierarchy
Indicates that a language served as the traditional or historically established language used by a particular hierarchy or hierarchical institution.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 1, 2026, 12:30 a.m.