Triple

T37303521
Position Surface form Disambiguated ID Type / Status
Subject Talos I E926018 entity
Predicate hasSection P35 FINISHED
Object Psychotronics
Psychotronics is a research and containment division aboard the Talos I space station in the game Prey, focused on studying and exploiting the alien Typhon’s psychic and neurological abilities.
E2221984 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: Psychotronics | Statement: [Talos I, hasSection, Psychotronics]
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: Psychotronics
Triple: [Talos I, hasSection, Psychotronics]
Generated description
Psychotronics is a research and containment division aboard the Talos I space station in the game Prey, focused on studying and exploiting the alien Typhon’s psychic and neurological abilities.

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_69f76eb1bc508190924e9fa5d8acdeb3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb5b1304d08190a3e86888bf1c2b05 completed May 6, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40638f21b48190b51ed34a4460832f completed June 27, 2026, 11:58 p.m.
NEDg Description generation batch_6a40649da7188190907f2c12b6a9ce1e completed June 28, 2026, 12:02 a.m.
NED2 Entity disambiguation (via description) batch_6a40655bd8d881908a0824fbd19562cd completed June 28, 2026, 12:05 a.m.
Created at: May 3, 2026, 4:16 p.m.