Triple

T29248626
Position Surface form Disambiguated ID Type / Status
Subject MPE/iX E741501 entity
Predicate integratedDatabase P52665 FINISHED
Object TurboIMAGE
TurboIMAGE is a hierarchical network database management system developed by Hewlett-Packard for its HP 3000 MPE/iX operating environment.
E1859940 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: TurboIMAGE | Statement: [MPE/iX, integratedDatabase, TurboIMAGE]
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: TurboIMAGE
Triple: [MPE/iX, integratedDatabase, TurboIMAGE]
Generated description
TurboIMAGE is a hierarchical network database management system developed by Hewlett-Packard for its HP 3000 MPE/iX operating environment.

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_69f0911eba2c8190b07cd2fdf91422c9 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f6aa232a5c8190bd09a96cdc552c7a completed May 3, 2026, 1:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a258925827c819094b5cb59e98790b4 completed June 7, 2026, 3:07 p.m.
NEDg Description generation batch_6a2594cd74408190b337810ceac39724 completed June 7, 2026, 3:57 p.m.
NED2 Entity disambiguation (via description) batch_6a2599021d10819083fc8e0a0c13b189 completed June 7, 2026, 4:14 p.m.
Created at: April 28, 2026, 12:33 p.m.