Triple

T29488283
Position Surface form Disambiguated ID Type / Status
Subject Horace, Kansas E747991 entity
Predicate hasRegionCodeFIPSState P136034 FINISHED
Object 20 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: 20 | Statement: [Horace, Kansas, hasRegionCodeFIPSState, 20]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegionCodeFIPSState
Context triple: [Horace, Kansas, hasRegionCodeFIPSState, 20]
  • A. FIPSCode
    Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
  • B. FIPSRegion
    Indicates that an entity is associated with a specific geographic region as defined by a FIPS (Federal Information Processing Standards) code.
  • C. USStateFIPSLocation chosen
    Indicates a locational relationship where a place or entity is situated within, or associated with, a U.S. state identified by its FIPS (Federal Information Processing Standards) code.
  • D. hasISO3166-2CodePrefix
    Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
  • E. federalRegion
    Indicates that an entity is located within, administered by, or associated with a specific federal region or federal-level administrative division.
  • 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_69f0bd43ba30819095eb1cfc3adf525c completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fffc783b648190bcd7df017514d206 completed May 10, 2026, 3:33 a.m.
PD Predicate disambiguation batch_69fffc03fa24819099e12413dc6e0afd completed May 10, 2026, 3:31 a.m.
Created at: April 28, 2026, 4:11 p.m.