Triple

T33196453
Position Surface form Disambiguated ID Type / Status
Subject George W. Steele E849771 entity
Predicate hasTerritorialGovernorship P133454 FINISHED
Object Oklahoma Territory 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: Oklahoma Territory | Statement: [George W. Steele, hasTerritorialGovernorship, Oklahoma Territory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTerritorialGovernorship
Context triple: [George W. Steele, hasTerritorialGovernorship, Oklahoma Territory]
  • A. hasRegionalGovernor
    Indicates that a region is administered or overseen by a specific governor responsible for its governance.
  • B. territorialGovernorOf chosen
    Indicates that one entity serves as the official governing authority or administrator of a specified territory.
  • C. hasResidentGovernor
    Indicates that a place or territory has an officially appointed governor who resides there and exercises governing authority over it.
  • D. hasRankOfGovernor
    Indicates that an entity holds the official position or rank of governor in relation to a specified jurisdiction or organization.
  • E. hasProvinceGovernment
    Indicates that a province is administered or governed by a specific provincial government authority.
  • 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_69f3495efedc8190843a5728089544b9 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fd6f9d600c8190acf495b7fc632e4b completed May 8, 2026, 5:07 a.m.
PD Predicate disambiguation batch_69fd6e98a2948190a9f78c415ad23b8c completed May 8, 2026, 5:03 a.m.
Created at: May 1, 2026, 1:29 a.m.