Triple

T26549337
Position Surface form Disambiguated ID Type / Status
Subject Clark County, Kansas E671630 entity
Predicate hasUnincorporatedCommunity P6345 FINISHED
Object Englewood, Kansas
Englewood, Kansas is a small rural community located in Clark County in the south-central region of the U.S. state of Kansas.
E1731559 NE 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: Englewood, Kansas | Statement: [Clark County, Kansas, hasUnincorporatedCommunity, Englewood, Kansas]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Englewood, Kansas
Triple: [Clark County, Kansas, hasUnincorporatedCommunity, Englewood, Kansas]
Generated description
Englewood, Kansas is a small rural community located in Clark County in the south-central region of the U.S. state of Kansas.

Provenance (5 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_69eeb32163f08190af5f81282738e27a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f614391e4c81908b14843830640ad1 completed May 2, 2026, 3:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11c81bd59c8190ae3d79520956b166 completed May 23, 2026, 3:30 p.m.
NEDg Description generation batch_6a11c8f290bc8190bfa1990ee7119516 completed May 23, 2026, 3:34 p.m.
NED2 Entity disambiguation (via description) batch_6a11ca61b1408190ab4bda33e53cb27c completed May 23, 2026, 3:40 p.m.
Created at: April 27, 2026, 1:46 a.m.