Triple
T26223707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adityapur Industrial Area |
E655831
|
entity |
| Predicate | supportsIndustrialCenter |
P194933
|
FINISHED |
| Object | Jamshedpur |
—
|
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: Jamshedpur | Statement: [Adityapur Industrial Area, supportsIndustrialCenter, Jamshedpur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIndustrialCenter Context triple: [Adityapur Industrial Area, supportsIndustrialCenter, Jamshedpur]
-
A.
isIndustrialCenter
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
B.
connectsIndustrialCenter
Indicates a relationship where one entity serves as a link or route that joins or provides access between industrial centers.
-
C.
servesIndustrialCity
Indicates that something functions to provide services, support, or utility to an industrial city.
-
D.
industrialComplex
Indicates a relationship where a facility or site functions as a large-scale, integrated center for industrial production, processing, or related operations.
-
E.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: April 26, 2026, 8:57 p.m.