Triple

T37513255
Position Surface form Disambiguated ID Type / Status
Subject King Leoric E932567 entity
Predicate associatedLocation P37 FINISHED
Object Leoric's Passage
Leoric's Passage is an underground dungeon area in the Diablo video game series, located beneath King Leoric's domain and often serving as an early-game exploration and combat zone.
E2231919 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: Leoric's Passage | Statement: [King Leoric, associatedLocation, Leoric's Passage]
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: Leoric's Passage
Triple: [King Leoric, associatedLocation, Leoric's Passage]
Generated description
Leoric's Passage is an underground dungeon area in the Diablo video game series, located beneath King Leoric's domain and often serving as an early-game exploration and combat zone.

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_69f76ec730988190b5aa4f9cb9afd518 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba3ca516881908b5324127b5c5d69 completed May 6, 2026, 8:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a409efcf1dc8190af996121148fe50f completed June 28, 2026, 4:11 a.m.
NEDg Description generation batch_6a409fc3135c819088b48c78791b7672 completed June 28, 2026, 4:14 a.m.
NED2 Entity disambiguation (via description) batch_6a40a0aa945c81909a9b8ab5b797d45a completed June 28, 2026, 4:18 a.m.
Created at: May 3, 2026, 4:17 p.m.