Triple

T9776540
Position Surface form Disambiguated ID Type / Status
Subject Routeburn Flats Campsite E237260 entity
Predicate mobileCoverage P46630 FINISHED
Object limited or no mobile phone coverage 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: limited or no mobile phone coverage | Statement: [Routeburn Flats Campsite, mobileCoverage, limited or no mobile phone coverage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mobileCoverage
Context triple: [Routeburn Flats Campsite, mobileCoverage, limited or no mobile phone coverage]
  • A. networkCoverage
    Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
  • B. dataCoverage
    Indicates the extent or proportion of relevant data that is included, captured, or represented within a given dataset or system.
  • C. digitalCoverage
    Indicates that one entity provides or has access to digital services, connectivity, or online resources for another entity or within a specified area.
  • D. mapCoverage
    Indicates the extent or area that is represented, covered, or included by a particular map.
  • E. hasCellService chosen
    Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
  • 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_69ca84d975a08190aab25b02a89bdab3 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda133ef548190aaecdf49de9c5aa8 completed April 1, 2026, 10:50 p.m.
PD Predicate disambiguation batch_69cd03d3b68c81909e570401a891b9f2 completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:26 p.m.