Triple

T29174744
Position Surface form Disambiguated ID Type / Status
Subject Minot International Airport E739575 entity
Predicate operator P179 FINISHED
Object City of Minot
The City of Minot is a municipal government in North Dakota responsible for providing local services, infrastructure, and administration for the community of Minot.
E1855082 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: City of Minot | Statement: [Minot International Airport, operator, City of Minot]
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: City of Minot
Triple: [Minot International Airport, operator, City of Minot]
Generated description
The City of Minot is a municipal government in North Dakota responsible for providing local services, infrastructure, and administration for the community of Minot.

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_69f07cb6394c8190ab7842c48e699e2a completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6633f165481909e68b69dea0a98a8 completed May 2, 2026, 8:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2569b220dc819099325e75c7516fea completed June 7, 2026, 12:53 p.m.
NEDg Description generation batch_6a256ec6d4a08190bf2a4a8bf0d444b4 completed June 7, 2026, 1:14 p.m.
NED2 Entity disambiguation (via description) batch_6a2572b365748190bcfad1dcd351f1f3 completed June 7, 2026, 1:31 p.m.
Created at: April 28, 2026, 11:54 a.m.