Triple

T31917694
Position Surface form Disambiguated ID Type / Status
Subject Morgan, Utah E814878 entity
Predicate countyGovernmentLocatedIn P78431 FINISHED
Object Morgan County Courthouse
The Morgan County Courthouse is the primary government and judicial building serving Morgan County in the city of Morgan, Utah.
E1985896 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: Morgan County Courthouse | Statement: [Morgan, Utah, countyGovernmentLocatedIn, Morgan County Courthouse]
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: Morgan County Courthouse
Triple: [Morgan, Utah, countyGovernmentLocatedIn, Morgan County Courthouse]
Generated description
The Morgan County Courthouse is the primary government and judicial building serving Morgan County in the city of Morgan, Utah.

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_69f348f109d88190b5005372c53d2fcd completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b1f1dc708190a95613f030b963ae completed May 3, 2026, 2:24 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2eb136e510819098db7d0e36be0915 completed June 14, 2026, 1:48 p.m.
NEDg Description generation batch_6a2eb1b9f69081908acd2ea6a68b7b1b completed June 14, 2026, 1:50 p.m.
NED2 Entity disambiguation (via description) batch_6a2eb20d3f8c81909fa01e2e1e1c0604 completed June 14, 2026, 1:52 p.m.
Created at: May 1, 2026, 12:02 a.m.