Triple

T34957432
Position Surface form Disambiguated ID Type / Status
Subject Delta Flyer E1008156 entity
Predicate designedBy P184 FINISHED
Object Harry Kim
Harry Kim is a Starfleet operations officer aboard the USS Voyager in Star Trek: Voyager, known for his technical expertise and key role in the ship’s journey through the Delta Quadrant.
E309067 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: Harry Kim | Statement: [Delta Flyer, designedBy, Harry Kim]
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: Harry Kim
Triple: [Delta Flyer, designedBy, Harry Kim]
Generated description
Harry Kim is a Starfleet operations officer aboard the USS Voyager in Star Trek: Voyager, known for his technical expertise and key role in the ship’s journey through the Delta Quadrant.

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_69f76dc69564819099e9e78aed6ff0a6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7841dc4148190b04c5fbcd0d82ff8 completed May 3, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37d93a095481908745c5be5976e723 completed June 21, 2026, 12:29 p.m.
NEDg Description generation batch_6a37db928b508190af4f1c1285e80752 completed June 21, 2026, 12:39 p.m.
NED2 Entity disambiguation (via description) batch_6a37dc0c0a5081908ce1002b7181b433 completed June 21, 2026, 12:41 p.m.
Created at: May 3, 2026, 4 p.m.