Triple

T25228850
Position Surface form Disambiguated ID Type / Status
Subject PAF Base Minhas E632167 entity
Predicate hostsUnit P3556 FINISHED
Object No. 14 Squadron Pakistan Air Force
No. 14 Squadron Pakistan Air Force is a combat squadron of the Pakistan Air Force known for its fighter operations and long-standing service history.
E1676246 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: No. 14 Squadron Pakistan Air Force | Statement: [PAF Base Minhas, hostsUnit, No. 14 Squadron Pakistan Air Force]
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: No. 14 Squadron Pakistan Air Force
Triple: [PAF Base Minhas, hostsUnit, No. 14 Squadron Pakistan Air Force]
Generated description
No. 14 Squadron Pakistan Air Force is a combat squadron of the Pakistan Air Force known for its fighter operations and long-standing service history.

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_69e75a8e0f688190a7aebe9a4815e25b completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47cc608bc8190b3ae866dafd25c4f completed May 1, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1075cd32208190909e1ea6b9c793b7 completed May 22, 2026, 3:27 p.m.
NEDg Description generation batch_6a1076991b208190945d037fd9eef5f2 completed May 22, 2026, 3:30 p.m.
NED2 Entity disambiguation (via description) batch_6a1077bbf9448190bee4351dcb985c0c completed May 22, 2026, 3:35 p.m.
Created at: April 21, 2026, 1:04 p.m.