Triple

T36621030
Position Surface form Disambiguated ID Type / Status
Subject West Bank of Luxor E904036 entity
Predicate contains P35 FINISHED
Object El-Assasif necropolis
El-Assasif necropolis is an ancient Egyptian burial ground near Luxor notable for its rock-cut tombs of high officials and elites from the Middle Kingdom through the Late Period.
E2194860 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: El-Assasif necropolis | Statement: [West Bank of Luxor, contains, El-Assasif necropolis]
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: El-Assasif necropolis
Triple: [West Bank of Luxor, contains, El-Assasif necropolis]
Generated description
El-Assasif necropolis is an ancient Egyptian burial ground near Luxor notable for its rock-cut tombs of high officials and elites from the Middle Kingdom through the Late Period.

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_69f76e6ae750819096911e6e2d4d12c5 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c4ace7b8819096462c6577fa11d1 completed May 3, 2026, 9:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a20bf919081909761e5beacb663b0 completed June 23, 2026, 5:59 a.m.
NEDg Description generation batch_6a3a21673a0c8190a1b8e1c579aa2caa completed June 23, 2026, 6:02 a.m.
NED2 Entity disambiguation (via description) batch_6a3a2e048594819082e6baf80319570e completed June 23, 2026, 6:56 a.m.
Created at: May 3, 2026, 4:11 p.m.