Triple

T34986051
Position Surface form Disambiguated ID Type / Status
Subject Type-11 shuttlecraft E1008948 entity
Predicate registryContext P182171 FINISHED
Object USS Enterprise-E shuttle complement LITERAL 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 Enterprise-E shuttle complement | Statement: [Type-11 shuttlecraft, registryContext, USS Enterprise-E shuttle complement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: registryContext
Context triple: [Type-11 shuttlecraft, registryContext, USS Enterprise-E shuttle complement]
  • A. registrationContext
    Indicates the situational or environmental context under which a registration event occurs, such as conditions, purpose, or setting.
  • B. regionContext
    Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
  • C. registryType
    Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
  • D. registryDependency
    Indicates that one entity depends on another entity being registered or present in a registry in order to function or be valid.
  • E. ringSystemContext
    Indicates that an entity’s ring system is being described or analyzed within a specific contextual framework (such as observational, physical, or environmental conditions).
  • F. None of above. chosen

Provenance (4 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_69f78710282c81909146dc0be91e983f completed May 3, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f784162134819098413482ef52042f completed May 3, 2026, 5:21 p.m.
PDg Predicate description generation batch_69f7870dfe108190996c0c68630edc7f completed May 3, 2026, 5:34 p.m.
Created at: May 3, 2026, 4:01 p.m.