Triple
T12159592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dahisar |
E289668
|
entity |
| Predicate | hasMunicipalWard |
P14475
|
FINISHED |
| Object | R North ward |
—
|
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: R North ward | Statement: [Dahisar, hasMunicipalWard, R North ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalWard Context triple: [Dahisar, hasMunicipalWard, R North ward]
-
A.
hasMunicipalDistrict
Indicates that an administrative entity includes or is divided into one or more municipal districts as its subordinate units.
-
B.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
-
C.
hasMunicipalPart
Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
-
D.
containsWard
chosen
Indicates that one entity includes, encompasses, or has within it a ward (such as a district, division, or dependent person) as part of its scope or responsibility.
-
E.
isMunicipalCorporationOf
Indicates that an entity functions as the municipal governing body responsible for administering and managing the affairs of a specified city or urban 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.