Triple
T25331770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahishya |
E635168
|
entity |
| Predicate | hasRegionOfConcentration |
P70368
|
FINISHED |
| Object | southern West Bengal |
—
|
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: southern West Bengal | Statement: [Mahishya, hasRegionOfConcentration, southern West Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionOfConcentration Context triple: [Mahishya, hasRegionOfConcentration, southern West Bengal]
-
A.
hasConcentration
Indicates that one entity possesses or exhibits a specific level, strength, or density of another substance, property, or attribute.
-
B.
hasCoordinateConcentration
Indicates that an entity has a specific concentration value associated with a particular spatial or coordinate location.
-
C.
hasPopulationConcentrationIn
chosen
Indicates that a population is densely or significantly clustered within a specified geographic area or region.
-
D.
hasCentralRegion
Indicates that an entity possesses or is associated with a primary or central area within its overall structure or domain.
-
E.
hasRegionCenter
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 21, 2026, 1:30 p.m.