Triple
T27569817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Development Region |
E696000
|
entity |
| Predicate | containsZone |
P123563
|
FINISHED |
| Object | Mechi Zone |
—
|
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: Mechi Zone | Statement: [Eastern Development Region, containsZone, Mechi Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsZone Context triple: [Eastern Development Region, containsZone, Mechi Zone]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
includesMetropolitanZone
Indicates that one geographic or administrative area contains or encompasses a designated metropolitan zone within its boundaries.
-
C.
isPrimarilyZonedFor
Indicates that a particular area or property is designated mainly for a specific type of land use under zoning regulations.
-
D.
regionContains
chosen
Indicates that one region spatially encompasses or includes another region within its boundaries.
-
E.
hasZoneStatus
Indicates that a specified zone currently possesses a particular status or condition.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 27, 2026, 1:43 p.m.