Triple

T37969762
Position Surface form Disambiguated ID Type / Status
Subject United States House of Representatives seat for Alaska E947246 entity
Predicate startDateAsStateDistrict P59525 FINISHED
Object 1959-01-03 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: 1959-01-03 | Statement: [United States House of Representatives seat for Alaska, startDateAsStateDistrict, 1959-01-03]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: startDateAsStateDistrict
Context triple: [United States House of Representatives seat for Alaska, startDateAsStateDistrict, 1959-01-03]
  • A. startDateAsElectoralRegion chosen
    Indicates the date on which an entity first began to function or be recognized as an electoral region.
  • B. hasStateOrDistrict
    Indicates that an entity is associated with, located in, or belongs to a particular state or district.
  • C. federalDistrictSince
    Indicates that an entity has held the status of a federal district starting from a specified point in time.
  • D. statePowerStartDate
    Indicates the date on which a state or governing authority first began to exercise its official power or jurisdiction.
  • E. servesStateOrDistrict
    Indicates that an entity holds a role or position in service to a specific state or electoral district.
  • 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_69f76ef7db908190bba6086673a32300 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a0154b16a3c8190b808a460ae3a91ac completed May 11, 2026, 4:01 a.m.
PD Predicate disambiguation batch_6a01539f19d88190b2de63f5262b1074 completed May 11, 2026, 3:57 a.m.
Created at: May 3, 2026, 4:20 p.m.