Triple
T23395441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalgaon division (informal) |
E559344
|
entity |
| Predicate | hasCoreDistrict |
P14400
|
FINISHED |
| Object | Jalgaon district |
—
|
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: Jalgaon district | Statement: [Jalgaon division (informal), hasCoreDistrict, Jalgaon district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreDistrict Context triple: [Jalgaon division (informal), hasCoreDistrict, Jalgaon district]
-
A.
hasCoreTown
Indicates that an entity possesses or is associated with a primary or central town that serves as its main urban center.
-
B.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
-
C.
hasCoreArea
chosen
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
D.
isDowntownCoreOf
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
-
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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4db1c888190ace5d58bcc8645c1 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.