Triple

T34976203
Position Surface form Disambiguated ID Type / Status
Subject USS Enterprise (NCC-1701-D) E1008682 entity
Predicate captain P884 FINISHED
Object Edward Jellico
Edward Jellico is a Starfleet officer in the Star Trek universe who temporarily commanded the USS Enterprise-D during a critical confrontation with the Cardassians.
E2130857 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: Edward Jellico | Statement: [USS Enterprise (NCC-1701-D), captain, Edward Jellico]
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: Edward Jellico
Triple: [USS Enterprise (NCC-1701-D), captain, Edward Jellico]
Generated description
Edward Jellico is a Starfleet officer in the Star Trek universe who temporarily commanded the USS Enterprise-D during a critical confrontation with the Cardassians.

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_69f76dc78a308190a1ac29ad4a9a4895 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78469e75881908ef6f045d13c070d completed May 3, 2026, 5:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3803ee73348190b377b15cf93ac660 completed June 21, 2026, 3:31 p.m.
NEDg Description generation batch_6a3804672aa481909e0fab282f6d7a51 completed June 21, 2026, 3:33 p.m.
NED2 Entity disambiguation (via description) batch_6a38051421208190a195f5eef3667f47 completed June 21, 2026, 3:36 p.m.
Created at: May 3, 2026, 4:01 p.m.