Triple
T38619826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharan |
E936836
|
entity |
| Predicate | hasDeFactoNationalLanguageCountry |
P201305
|
FINISHED |
| Object | Urdu |
—
|
NE NERFINISHED |
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: Urdu | Statement: [Kharan, hasDeFactoNationalLanguageCountry, Urdu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeFactoNationalLanguageCountry Context triple: [Kharan, hasDeFactoNationalLanguageCountry, Urdu]
-
A.
hasOfficialCountryLanguage
Indicates that a country recognizes a particular language as one of its official languages for governmental or legal purposes.
-
B.
hasNotableLanguageWithOfficialStatusIn
Indicates that a language holds an officially recognized and notable status within a specified jurisdiction or region.
-
C.
isSpokenLanguageOf
Indicates that a particular language is used as the spoken language by a specified person, group, or community.
-
D.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
E.
hasCountryOfficialLanguageForm
Indicates that a country uses a specific official language in a particular written or standardized form.
- F. None of above. chosen
Provenance (4 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
| PDg | Predicate description generation | batch_69ffe6e21f748190a18dfe0878d397f7 |
completed | May 10, 2026, 2:01 a.m. |
Created at: May 3, 2026, 4:32 p.m.