Triple

T27002156
Position Surface form Disambiguated ID Type / Status
Subject Elkhorn, Nebraska E680138 entity
Predicate governmentAfterAnnexation P193591 FINISHED
Object governed by City of Omaha NE NERFINISHED

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: governed by City of Omaha | Statement: [Elkhorn, Nebraska, governmentAfterAnnexation, governed by City of Omaha]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governmentAfterAnnexation
Context triple: [Elkhorn, Nebraska, governmentAfterAnnexation, governed by City of Omaha]
  • A. statusAfterAnnexation
    Indicates the legal or political condition an entity holds following its annexation by another entity.
  • B. residenceAfterAnnexation
    Indicates that an entity’s place of residence is located in a territory after that territory has been annexed by another political authority.
  • C. titleAfterAnnexation
    Indicates that an entity holds or is assigned a particular title specifically in the period following an annexation event.
  • D. positionOnAnnexation
    Indicates a stance or viewpoint that an entity holds regarding the act or policy of annexing a territory or region.
  • E. annexationPolicy
    Indicates a policy or practice of formally incorporating one territory into the jurisdiction or sovereignty of another.
  • F. None of above. chosen

Provenance (4 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_69eeeb52908c8190bd246244686aa455 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69fd4d1854988190be093b103a681798 completed May 8, 2026, 2:40 a.m.
PD Predicate disambiguation batch_69fd4c8d1a188190897c24527337814a completed May 8, 2026, 2:38 a.m.
PDg Predicate description generation batch_69fd4d16dd20819096957c40f43cd971 completed May 8, 2026, 2:40 a.m.
Created at: April 27, 2026, 6:58 a.m.