Triple

T29142447
Position Surface form Disambiguated ID Type / Status
Subject Amethyst, Princess of Gemworld E738672 entity
Predicate containsLocation P45140 FINISHED
Object House of Amethyst
House of Amethyst is the royal ruling house and ancestral domain of Princess Amethyst in DC Comics’ magical realm of Gemworld.
E1854492 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: House of Amethyst | Statement: [Amethyst, Princess of Gemworld, containsLocation, House of Amethyst]
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: House of Amethyst
Triple: [Amethyst, Princess of Gemworld, containsLocation, House of Amethyst]
Generated description
House of Amethyst is the royal ruling house and ancestral domain of Princess Amethyst in DC Comics’ magical realm of Gemworld.

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_69f07cb3adb48190a9e0e169cd026634 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f662707bfc819093d188364a088311 completed May 2, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25505a8bcc81908e70d1ea8fe21d90 completed June 7, 2026, 11:04 a.m.
NEDg Description generation batch_6a25549cc6548190937807666cda7b6f completed June 7, 2026, 11:23 a.m.
NED2 Entity disambiguation (via description) batch_6a255fff7c98819080aa4713ce278a9c completed June 7, 2026, 12:11 p.m.
Created at: April 28, 2026, 11:37 a.m.