Triple
T7531683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | बरामती |
E178036
|
entity |
| Predicate | औद्योगिक क्षेत्र |
P68164
|
FINISHED |
| Object | MIDC औद्योगिक वसाहत |
—
|
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: MIDC औद्योगिक वसाहत | Statement: [बरामती, औद्योगिक क्षेत्र, MIDC औद्योगिक वसाहत]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: औद्योगिक क्षेत्र Context triple: [बरामती, औद्योगिक क्षेत्र, MIDC औद्योगिक वसाहत]
-
A.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
B.
isIndustrialAreaOf
chosen
Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
-
C.
isIndustrialRegion
Indicates that a given area functions primarily as a center of industrial activity, characterized by significant manufacturing, production, or related industrial operations.
-
D.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
E.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84753fc81908bee2013004ef5fb |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.