Triple
T1569614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coimbatore |
E33507
|
entity |
| Predicate | industrialCluster |
P20603
|
FINISHED |
| Object | textile mills |
—
|
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: textile mills | Statement: [Coimbatore, industrialCluster, textile mills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialCluster Context triple: [Coimbatore, industrialCluster, textile mills]
-
A.
isPartOfEconomicCluster
Indicates that an entity belongs to, or is included within, a larger economic cluster or grouping based on economic relationships or activities.
-
B.
isIndustrialCenter
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
C.
hasIndustrialSector
chosen
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
D.
hasIndustrialPark
Indicates that a location or entity possesses or contains an industrial park within its area or jurisdiction.
-
E.
industryConsortium
Indicates a collaborative association where multiple organizations formally join together within an industry to pursue shared goals, standards, or initiatives.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.