Triple

T16155616
Position Surface form Disambiguated ID Type / Status
Subject Lennox, South Dakota E392031 entity
Predicate hasCountySubdivisionType P36805 FINISHED
Object county 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: county | Statement: [Lennox, South Dakota, hasCountySubdivisionType, county]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCountySubdivisionType
Context triple: [Lennox, South Dakota, hasCountySubdivisionType, county]
  • A. isInCountySubdivision
    Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
  • B. hasNationalSubdivisionType
    Indicates that an entity is associated with a specific type or category of national-level administrative subdivision (e.g., state, province, region).
  • C. hasTypeOfSubdivision chosen
    Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
  • D. hasSubdivision
    Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
  • E. hasSubdivisionCode
    Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
  • 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_69d87f1c65e48190aa2b4c472e9bafc4 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21e5902a08190ad8694955ef6073a completed April 17, 2026, 11:49 a.m.
PD Predicate disambiguation batch_69e1828abb608190a99d86bce1d77de2 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 5:01 a.m.