Triple
T4008313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faridabad district |
E89579
|
entity |
| Predicate | industrialCategory |
P53889
|
FINISHED |
| Object | major industrial hub in Haryana |
—
|
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: major industrial hub in Haryana | Statement: [Faridabad district, industrialCategory, major industrial hub in Haryana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialCategory Context triple: [Faridabad district, industrialCategory, major industrial hub in Haryana]
-
A.
industryCenter
Indicates that a location functions as a primary hub or focal point for industrial activity or production.
-
B.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
C.
hasIndustrialCompany
Indicates that one entity possesses, controls, or is associated with an industrial company.
-
D.
usedInIndustry
Indicates that something is employed or applied within a particular industry or industrial sector.
-
E.
hasIndustrialPlant
Indicates that an entity possesses, operates, or is associated with an industrial plant facility.
- F. None of above. chosen
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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefaea76c48190add2e7cee180e8b1 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:34 p.m.