Triple

T25250571
Position Surface form Disambiguated ID Type / Status
Subject south-central North Dakota E632730 entity
Predicate containsCity P294 FINISHED
Object Hazen, North Dakota
Hazen, North Dakota is a small city in Mercer County known for its role in the region’s coal and energy industries and its proximity to Lake Sakakawea.
E1700562 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: Hazen, North Dakota | Statement: [south-central North Dakota, containsCity, Hazen, North Dakota]
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: Hazen, North Dakota
Triple: [south-central North Dakota, containsCity, Hazen, North Dakota]
Generated description
Hazen, North Dakota is a small city in Mercer County known for its role in the region’s coal and energy industries and its proximity to Lake Sakakawea.

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_69e75a8fdd3881909ba0b05aa5da92a7 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f4808ac0cc8190b19571d4c71b3025 completed May 1, 2026, 10:29 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10ec8508dc8190a7c38a9ebea0a2d4 completed May 22, 2026, 11:53 p.m.
NEDg Description generation batch_6a10edc67f448190b6f8da9b63fd6759 completed May 22, 2026, 11:59 p.m.
NED2 Entity disambiguation (via description) batch_6a10ef3e35188190806530f76d78e331 completed May 23, 2026, 12:05 a.m.
Created at: April 21, 2026, 1:11 p.m.