Triple
T3177746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Nicobar Biosphere Reserve |
E66504
|
entity |
| Predicate | hasZonation |
P36294
|
FINISHED |
| Object | core zone |
—
|
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: core zone | Statement: [Great Nicobar Biosphere Reserve, hasZonation, core zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZonation Context triple: [Great Nicobar Biosphere Reserve, hasZonation, core zone]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
hasDRSZones
Indicates that one entity possesses, defines, or is associated with specific DRS (Disaster Recovery Site or similarly defined) zones.
-
C.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
D.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
E.
zoneType
chosen
Indicates the classification or category of a zone that specifies its type or functional designation.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69c2edc81908bfd23a1d5ce970e |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.