Triple

T20920814
Position Surface form Disambiguated ID Type / Status
Subject Sabana Abajo E515200 entity
Predicate hasCommercialZones P459 FINISHED
Object some commercial areas 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: some commercial areas | Statement: [Sabana Abajo, hasCommercialZones, some commercial areas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommercialZones
Context triple: [Sabana Abajo, hasCommercialZones, some commercial areas]
  • A. hasNoCommercialZone
    Indicates that the subject area or entity does not contain any designated commercial zone or commercial-use area.
  • B. hasLimitedCommercialAreas
    Indicates that the subject possesses or is characterized by commercial zones that are restricted in size, extent, or availability.
  • C. hasDRSZones
    Indicates that one entity possesses, defines, or is associated with specific DRS (Disaster Recovery Site or similarly defined) zones.
  • D. hasBusinessDistrict chosen
    Indicates that a place or administrative area contains or includes a designated business district within its boundaries.
  • E. hasIndustrialZoneAlong
    Indicates that an industrial zone is located adjacent to or extending along the length of a specified linear feature (such as a road, river, or boundary).
  • 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_69e0b4f9d5ec8190bb2bd27350ed341c completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6ec677338819081410cbaa2846260 completed April 21, 2026, 3:17 a.m.
PD Predicate disambiguation batch_69e5c9af1fe08190953366a466950140 completed April 20, 2026, 6:37 a.m.
Created at: April 16, 2026, 12:48 p.m.