Triple

T24298625
Position Surface form Disambiguated ID Type / Status
Subject Technique E606032 entity
Predicate hasPart P35 FINISHED
Object Dream Attack
Dream Attack is a specialized combat technique, likely used in a fictional or gaming context, that targets opponents through dream- or mind-based assaults.
 E1629729 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: Dream Attack | Statement: [Technique, hasPart, Dream Attack]
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: Dream Attack
Triple: [Technique, hasPart, Dream Attack]
Generated description
Dream Attack is a specialized combat technique, likely used in a fictional or gaming context, that targets opponents through dream- or mind-based assaults.

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_69e29549335881909cbf27adcaba1cf0 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f2915c520081908055941209f35da5 completed April 29, 2026, 11:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fc9d18e888190b45ea98b4b238a42 completed May 22, 2026, 3:13 a.m.
NEDg Description generation batch_6a0fcc7ba5c08190a1fe5a6155657453 completed May 22, 2026, 3:24 a.m.
NED2 Entity disambiguation (via description) batch_6a0fcd26c3c081908d9893c506f18063 completed May 22, 2026, 3:27 a.m.
Created at: April 18, 2026, 12:09 a.m.