Triple

T34161409
Position Surface form Disambiguated ID Type / Status
Subject Mesnie Hellequin E876285 entity
Predicate alsoKnownAs P39 FINISHED
Object Mesnée Hellequin
Mesnée Hellequin is a legendary spectral hunting procession from medieval European folklore, often associated with omens of death and the supernatural Wild Hunt.
E2113144 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: Mesnée Hellequin | Statement: [Mesnie Hellequin, alsoKnownAs, Mesnée Hellequin]
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: Mesnée Hellequin
Triple: [Mesnie Hellequin, alsoKnownAs, Mesnée Hellequin]
Generated description
Mesnée Hellequin is a legendary spectral hunting procession from medieval European folklore, often associated with omens of death and the supernatural Wild Hunt.

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_69f349ac987481908a8e6053f665bc8b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70fb9cd688190b231e5afb3a2f92b completed May 3, 2026, 9:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a376f8892c881909e53dc5a2aad9705 completed June 21, 2026, 4:58 a.m.
NEDg Description generation batch_6a37701da7a48190aa13ceb509274dd5 completed June 21, 2026, 5:01 a.m.
NED2 Entity disambiguation (via description) batch_6a37716ab2c48190b7c24792201885c8 completed June 21, 2026, 5:06 a.m.
Created at: May 1, 2026, 1:54 a.m.