Triple
T27859616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai Metropolitan Region |
E704187
|
entity |
| Predicate | hasMajorPlannedCity |
P21398
|
FINISHED |
| Object | Navi Mumbai |
—
|
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: Navi Mumbai | Statement: [Mumbai Metropolitan Region, hasMajorPlannedCity, Navi Mumbai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPlannedCity Context triple: [Mumbai Metropolitan Region, hasMajorPlannedCity, Navi Mumbai]
-
A.
hasPlannedCity
chosen
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
B.
isPlannedCity
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
-
C.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
D.
hasMetropolitanPlan
Indicates that an entity is associated with or governed by a designated metropolitan planning framework or strategy.
-
E.
cityOfPlanning
Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 27, 2026, 6:16 p.m.