Triple

T30537689
Position Surface form Disambiguated ID Type / Status
Subject 129th Operations Group E777192 entity
Predicate hasSubunit P747 FINISHED
Object 130th Rescue Squadron
The 130th Rescue Squadron is a unit of the California Air National Guard specializing in combat search and rescue and personnel recovery operations.
E1921454 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: 130th Rescue Squadron | Statement: [129th Operations Group, hasSubunit, 130th Rescue Squadron]
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: 130th Rescue Squadron
Triple: [129th Operations Group, hasSubunit, 130th Rescue Squadron]
Generated description
The 130th Rescue Squadron is a unit of the California Air National Guard specializing in combat search and rescue and personnel recovery operations.

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_69f2249d183c8190b79937c1768d2163 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f688520c60819081c3365a0f944326 completed May 2, 2026, 11:27 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2856f32f748190959bba830edc3c91 completed June 9, 2026, 6:09 p.m.
NEDg Description generation batch_6a2858c49eac8190ab62973857816e76 completed June 9, 2026, 6:17 p.m.
NED2 Entity disambiguation (via description) batch_6a285954e3208190a8bb4f6b023e11fd completed June 9, 2026, 6:20 p.m.
Created at: April 29, 2026, 8:19 p.m.