Triple
T26223685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamharia |
E655830
|
entity |
| Predicate | hasNearbyIndustrialAreas |
P20649
|
FINISHED |
| Object | industrial estates serving Jamshedpur region |
—
|
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: industrial estates serving Jamshedpur region | Statement: [Gamharia, hasNearbyIndustrialAreas, industrial estates serving Jamshedpur region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyIndustrialAreas Context triple: [Gamharia, hasNearbyIndustrialAreas, industrial estates serving Jamshedpur region]
-
A.
adjacentToIndustrialArea
Indicates that one entity is located directly next to or bordering an industrial area.
-
B.
hasNearbyIndustry
chosen
Indicates that an entity is located close to one or more industrial facilities or activities.
-
C.
containsIndustrialAreas
Indicates that one entity includes or encompasses industrial areas within its boundaries or scope.
-
D.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
-
E.
connectsToIndustrialArea
Indicates that one entity has a direct link, route, or access connection to an industrial area.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 26, 2026, 8:57 p.m.