Triple

T23874136
Position Surface form Disambiguated ID Type / Status
Subject Cherryvale, Kansas E592816 entity
Predicate hasOilIndustryHistory P40168 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: [Cherryvale, Kansas, hasOilIndustryHistory, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOilIndustryHistory
Context triple: [Cherryvale, Kansas, hasOilIndustryHistory, true]
  • A. isOilIndustryHub
    Indicates that a location serves as a central focal point for activities, infrastructure, and operations related to the oil industry.
  • B. containsOilField
    Indicates that one entity geographically includes or encompasses an oil field within its boundaries.
  • C. hasSignificantOilReservesInRegion
    Indicates that an entity possesses substantial oil reserves located within a specified geographic region.
  • D. hasNaturalResourceHistory chosen
    Indicates that there exists a documented history or record of natural resource–related events, uses, or conditions associated with an entity.
  • E. hasMajorOffshoreOilField
    Indicates that a country or region possesses at least one large, economically significant oil field located offshore in its territorial waters or exclusive economic zone.
  • 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_69e25d23a5c88190ae3999c70ca15e08 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1cbff91788190b7aabe285014b873 completed April 29, 2026, 9:14 a.m.
PD Predicate disambiguation batch_69f1614a65a88190bde1efb368a151e4 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:14 p.m.