Triple
T24801034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranjangaon, Maharashtra, India |
E620521
|
entity |
| Predicate | hasTypeOfZone |
P6793
|
FINISHED |
| Object | residential village area |
—
|
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: residential village area | Statement: [Ranjangaon, Maharashtra, India, hasTypeOfZone, residential village area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfZone Context triple: [Ranjangaon, Maharashtra, India, hasTypeOfZone, residential village area]
-
A.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
hasZoneStatus
Indicates that a specified zone currently possesses a particular status or condition.
-
C.
hasEconomicZoneType
Indicates the specific classification or category of economic zone associated with an entity.
-
D.
hasZoneStructure
Indicates that an entity possesses a defined internal division into zones or regions, each forming part of its overall structure.
-
E.
containsRegionType
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 4:49 a.m.