Triple
T34130903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Government in Jharkhand |
E875420
|
entity |
| Predicate | languageOfFunctioning |
P92545
|
FINISHED |
| Object | Hindi |
—
|
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: Hindi | Statement: [Central Government in Jharkhand, languageOfFunctioning, Hindi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfFunctioning Context triple: [Central Government in Jharkhand, languageOfFunctioning, Hindi]
-
A.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
B.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
C.
languageGroupSpoken
chosen
Indicates that a particular language group is spoken or used for communication by an entity.
-
D.
parentLanguage
Indicates that one language is the ancestral or source language from which another language is derived or historically developed.
-
E.
languageOfSelfDescription
Indicates the language in which an entity describes itself (e.g., in its self-presentation, profile, or official self-authored text).
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 1, 2026, 1:53 a.m.