Triple
T38313784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bal Mithai |
E1033767
|
entity |
| Predicate | originatesFromHistoricalRegion |
P201038
|
FINISHED |
| Object | Kumaon division of Uttarakhand |
E78950
|
NE 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: Kumaon division of Uttarakhand | Statement: [Bal Mithai, originatesFromHistoricalRegion, Kumaon division of Uttarakhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromHistoricalRegion Context triple: [Bal Mithai, originatesFromHistoricalRegion, Kumaon division of Uttarakhand]
-
A.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
B.
historicalOriginArea
chosen
Indicates the geographic area from which something originally emerged or historically originated.
-
C.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
D.
historicalRegionUsedFor
Indicates that a historical region served as the location or area of use for a particular activity, purpose, or entity.
-
E.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
- F. None of above.
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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b292cf508190ab0cafce35c140e9 |
completed | June 28, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.