Triple

T34986079
Position Surface form Disambiguated ID Type / Status
Subject Excelsior class E1008949 entity
Predicate notableShip P3345 FINISHED
Object USS Gorkon
The USS Gorkon is a prominent Excelsior-class starship in the Star Trek universe, often depicted in fan-created and expanded-universe stories as a notable Federation vessel.
E2125243 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: USS Gorkon | Statement: [Excelsior class, notableShip, USS Gorkon]
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: USS Gorkon
Triple: [Excelsior class, notableShip, USS Gorkon]
Generated description
The USS Gorkon is a prominent Excelsior-class starship in the Star Trek universe, often depicted in fan-created and expanded-universe stories as a notable Federation vessel.

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_69f76dc844a48190881951fffb83d17e completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7849d996481909baf92a2d8b69133 completed May 3, 2026, 5:23 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37cfd9ea808190ad828b8dddbba8f8 completed June 21, 2026, 11:49 a.m.
NEDg Description generation batch_6a37d0a8cc748190989640faa3a1c600 completed June 21, 2026, 11:53 a.m.
NED2 Entity disambiguation (via description) batch_6a37d140ec9481909f08dbd8c40d1ec7 completed June 21, 2026, 11:55 a.m.
Created at: May 3, 2026, 4:01 p.m.