Triple

T34858192
Position Surface form Disambiguated ID Type / Status
Subject 509th Medical Group E1004782 entity
Predicate hasAbbreviation P43 FINISHED
Object 509 MDG
509 MDG is the medical group responsible for providing healthcare services and support to personnel and beneficiaries associated with the 509th Bomb Wing at Whiteman Air Force Base.
E2115618 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: 509 MDG | Statement: [509th Medical Group, hasAbbreviation, 509 MDG]
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: 509 MDG
Triple: [509th Medical Group, hasAbbreviation, 509 MDG]
Generated description
509 MDG is the medical group responsible for providing healthcare services and support to personnel and beneficiaries associated with the 509th Bomb Wing at Whiteman Air Force Base.

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_69f76dba76f0819090643cba102c41ec completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7816325588190ac2180db5522a643 completed May 3, 2026, 5:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37795ca3408190a89af6b177cba73f completed June 21, 2026, 5:40 a.m.
NEDg Description generation batch_6a377ab8b5308190982af72170eef223 completed June 21, 2026, 5:46 a.m.
NED2 Entity disambiguation (via description) batch_6a377b68e81c8190945fc86d705cb151 completed June 21, 2026, 5:49 a.m.
Created at: May 3, 2026, 4 p.m.