Triple

T25224335
Position Surface form Disambiguated ID Type / Status
Subject California-class starship E632050 entity
Predicate hasNotableExample P1259 FINISHED
Object USS Sacramento
USS Sacramento is a notable example of the California-class starships in the Star Trek universe, recognized for its role within Starfleet’s 24th-century fleet.
E1886457 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 Sacramento | Statement: [California-class starship, hasNotableExample, USS Sacramento]
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 Sacramento
Triple: [California-class starship, hasNotableExample, USS Sacramento]
Generated description
USS Sacramento is a notable example of the California-class starships in the Star Trek universe, recognized for its role within Starfleet’s 24th-century fleet.

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_69e75a8e0f688190a7aebe9a4815e25b completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47cc23da88190bad7b9a28e09898b completed May 1, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a26e5c464c0819097a6416f33ee907e completed June 8, 2026, 3:54 p.m.
NEDg Description generation batch_6a26e6e147d081909cd31eda74a95a11 completed June 8, 2026, 3:59 p.m.
NED2 Entity disambiguation (via description) batch_6a26eabd98e081908d444da8db7f2183 completed June 8, 2026, 4:15 p.m.
Created at: April 21, 2026, 1:03 p.m.