Triple

T28398048
Position Surface form Disambiguated ID Type / Status
Subject Prince Nayef bin Abdulaziz International Airport E719331 entity
Predicate alternativeName P39 FINISHED
Object Al-Qassim Airport
Al-Qassim Airport is a regional international airport in Saudi Arabia serving the Al-Qassim Province and surrounding areas.
E1820100 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: Al-Qassim Airport | Statement: [Prince Nayef bin Abdulaziz International Airport, alternativeName, Al-Qassim Airport]
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: Al-Qassim Airport
Triple: [Prince Nayef bin Abdulaziz International Airport, alternativeName, Al-Qassim Airport]
Generated description
Al-Qassim Airport is a regional international airport in Saudi Arabia serving the Al-Qassim Province and surrounding areas.

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_69eff6efd1b08190ae3cefd4f11388a2 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64cf1aa7c8190b146b26dd4291025 completed May 2, 2026, 7:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1641766f98819093b9d83b6edbeaf6 completed May 27, 2026, 12:57 a.m.
NEDg Description generation batch_6a1641ff20fc819087e9e4e07ff41442 completed May 27, 2026, 12:59 a.m.
NED2 Entity disambiguation (via description) batch_6a16453193948190864ad3f56efe7866 completed May 27, 2026, 1:13 a.m.
Created at: April 28, 2026, 1:18 a.m.