Triple
T29286593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolayat tehsil |
E742529
|
entity |
| Predicate | usesAdditionalOfficialLanguage |
P5601
|
FINISHED |
| Object | Rajasthani |
—
|
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: Rajasthani | Statement: [Kolayat tehsil, usesAdditionalOfficialLanguage, Rajasthani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAdditionalOfficialLanguage Context triple: [Kolayat tehsil, usesAdditionalOfficialLanguage, Rajasthani]
-
A.
additionalOfficialLanguage
chosen
Indicates that an entity has another language, beyond its primary one, that holds official or formally recognized status.
-
B.
usesOfficialLanguageOf
Indicates that one entity adopts and employs the official language of another entity for communication or formal purposes.
-
C.
hasOfficialCountryLanguage
Indicates that a country recognizes a particular language as one of its official languages for governmental or legal purposes.
-
D.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
E.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 12:58 p.m.