Triple
T35101342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Brahmin and Chhetri |
E1013024
|
entity |
| Predicate | stateLanguageAssociation |
P13499
|
FINISHED |
| Object | standard Nepali 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: standard Nepali language | Statement: [Hill Brahmin and Chhetri, stateLanguageAssociation, standard Nepali language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateLanguageAssociation Context triple: [Hill Brahmin and Chhetri, stateLanguageAssociation, standard Nepali language]
-
A.
languageAssociation
Indicates an association or relationship between entities based on a language they use, represent, or are linked to.
-
B.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
C.
provinceNameLanguage
Indicates the language in which a province’s name is expressed.
-
D.
linguisticStatusOfArea
Indicates the linguistic status or condition that characterizes a particular geographic area.
-
E.
standardLanguageOf
chosen
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 3, 2026, 4:01 p.m.