Triple

T3257485
Position Surface form Disambiguated ID Type / Status
Subject Burnie E68331 entity
Predicate isRegionalCommercialHub P9422 FINISHED
Object true 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: true | Statement: [Burnie, isRegionalCommercialHub, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRegionalCommercialHub
Context triple: [Burnie, isRegionalCommercialHub, true]
  • A. isEconomicCenter
    Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
  • B. servesAsFocusCityFor
    Indicates that a city functions as a primary or designated focus city for an airline, organization, or transportation network, typically hosting significant but not hub-level operations or activities.
  • C. isMajorCenterOf
    Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
  • D. isCommercialHubIn chosen
    Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
  • E. isDowntownHub
    Indicates that a location functions as a central, primary hub within a city’s downtown 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_69ad858f74408190bcbd07f967cd7bd0 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaf6a46448190a7fa0ca83fa096f8 completed March 8, 2026, 5:18 p.m.
PD Predicate disambiguation batch_69ada41ae74081909a0d1d696be8e35e completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:09 p.m.