Triple
T27416134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhirna zone |
E692898
|
entity |
| Predicate | languageUsedForTourism |
P48682
|
FINISHED |
| Object | Hindi |
—
|
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: Hindi | Statement: [Jhirna zone, languageUsedForTourism, Hindi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedForTourism Context triple: [Jhirna zone, languageUsedForTourism, Hindi]
-
A.
languageUsedInTourism
chosen
Indicates that a particular language is used for communication and services within tourism activities or contexts.
-
B.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
C.
languageOfSurroundingCountry
Indicates that a language is the primary or commonly used language in the country surrounding a given place or region.
-
D.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
E.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 27, 2026, 12:34 p.m.