Triple

T30198552
Position Surface form Disambiguated ID Type / Status
Subject Ur-Nanshe E767701 entity
Predicate built P1028 FINISHED
Object temple of Inanna
The temple of Inanna was an ancient Mesopotamian sanctuary dedicated to the goddess of love, war, and fertility, serving as a major religious and cultural center in early Sumerian society.
E1905170 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: temple of Inanna | Statement: [Ur-Nanshe, built, temple of Inanna]
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: temple of Inanna
Triple: [Ur-Nanshe, built, temple of Inanna]
Generated description
The temple of Inanna was an ancient Mesopotamian sanctuary dedicated to the goddess of love, war, and fertility, serving as a major religious and cultural center in early Sumerian society.

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_69f2247db1108190835c0727c97637c3 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67fc333508190b65ece66b1b573f7 completed May 2, 2026, 10:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27643953708190a63f8057f6820d53 completed June 9, 2026, 12:54 a.m.
NEDg Description generation batch_6a2764f2c6588190b88039903b3d891c completed June 9, 2026, 12:57 a.m.
NED2 Entity disambiguation (via description) batch_6a2766191bf48190bc484ef33593dc28 completed June 9, 2026, 1:02 a.m.
Created at: April 29, 2026, 7:30 p.m.