Triple

T34537314
Position Surface form Disambiguated ID Type / Status
Subject Khmun E886704 entity
Predicate worshipPracticed P11149 FINISHED
Object Thoth cult
The Thoth cult was an ancient Egyptian religious tradition centered on the worship of Thoth, the god of wisdom, writing, and the moon, particularly prominent in the city of Khmun (Hermopolis).
E2100733 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: Thoth cult | Statement: [Khmun, worshipPracticed, Thoth cult]
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: Thoth cult
Triple: [Khmun, worshipPracticed, Thoth cult]
Generated description
The Thoth cult was an ancient Egyptian religious tradition centered on the worship of Thoth, the god of wisdom, writing, and the moon, particularly prominent in the city of Khmun (Hermopolis).

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_69f349ce5eb881909e431c670944aa68 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71feeedc081908468bf1e2e2ef3e0 completed May 3, 2026, 10:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3729ef2d4c819095bb50a341b6e9b6 completed June 21, 2026, 12:01 a.m.
NEDg Description generation batch_6a372a79cd588190a26e3ed4d9d36787 completed June 21, 2026, 12:04 a.m.
NED2 Entity disambiguation (via description) batch_6a372b0a68648190b17d8b4b171473cf completed June 21, 2026, 12:06 a.m.
Created at: May 1, 2026, 2:02 a.m.