Triple

T36439488
Position Surface form Disambiguated ID Type / Status
Subject Al Rashid E897687 entity
Predicate governedRegion P11585 FINISHED
Object Haʼil Emirate
The Haʼil Emirate was a historical Arabian principality centered on the city of Haʼil in northern Najd, ruled by the Al Rashid dynasty and long a key rival to the House of Saud.
E2184522 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: Haʼil Emirate | Statement: [Al Rashid, governedRegion, Haʼil Emirate]
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: Haʼil Emirate
Triple: [Al Rashid, governedRegion, Haʼil Emirate]
Generated description
The Haʼil Emirate was a historical Arabian principality centered on the city of Haʼil in northern Najd, ruled by the Al Rashid dynasty and long a key rival to the House of Saud.

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_69f76e56636481908eda808ab0273401 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bd6cd59c8190a18122dca3373f67 completed May 3, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39c41adb9481908a4afcca50497baf completed June 22, 2026, 11:24 p.m.
NEDg Description generation batch_6a39c9201a5c8190bc1b82dcf4aa5682 completed June 22, 2026, 11:45 p.m.
NED2 Entity disambiguation (via description) batch_6a39ca5dd72c8190b766df2cc3b8b319 completed June 22, 2026, 11:50 p.m.
Created at: May 3, 2026, 4:10 p.m.