Triple

T3946888
Position Surface form Disambiguated ID Type / Status
Subject Wendover, Utah E92167 entity
Predicate historicalUseNearby P30574 FINISHED
Object World War II bomber training 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: World War II bomber training | Statement: [Wendover, Utah, historicalUseNearby, World War II bomber training]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalUseNearby
Context triple: [Wendover, Utah, historicalUseNearby, World War II bomber training]
  • A. historicalServiceNear chosen
    Indicates that a historical service or event occurred in close spatial proximity to a specified location or entity.
  • B. nearbyHistoricalServiceFor
    Indicates that a historical service or facility is located close to a given reference entity or location.
  • C. historicUsePersistsIn
    Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
  • D. historicalLocationOf
    Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
  • E. historicalLocationNowIn
    Indicates that an entity’s historical location is now situated within the boundaries of another, current geographic or political entity.
  • 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_69aed965502c8190904ebad1203a4ae8 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef1515c688190a38332aedeed8a76 completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee764235081909309b3c982f322a9 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:24 p.m.