Triple
T28787536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Maharashtra |
E726855
|
entity |
| Predicate | hasRegionalCenterCity |
P86556
|
FINISHED |
| Object | Kolhapur |
—
|
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: Kolhapur | Statement: [Southern Maharashtra, hasRegionalCenterCity, Kolhapur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalCenterCity Context triple: [Southern Maharashtra, hasRegionalCenterCity, Kolhapur]
-
A.
servesAsRegionalCenterFor
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
-
B.
hasRegionalCenterNearby
Indicates that a regional center is located in close proximity to the referenced entity.
-
C.
hasRegionalCentresIn
chosen
Indicates that an entity maintains one or more regional centers located in the specified place or area.
-
D.
hadRegionalCenter
Indicates that an entity possessed, operated, or was associated with a specific regional center serving a defined geographic area.
-
E.
hasCentralRegion
Indicates that an entity possesses or is associated with a primary or central area within its overall structure or domain.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 28, 2026, 6:22 a.m.