Triple

T7457488
Position Surface form Disambiguated ID Type / Status
Subject Bridgman seal E172162 entity
Predicate sealingMechanism P77021 FINISHED
Object radial expansion of plastically deformed seal material 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: radial expansion of plastically deformed seal material | Statement: [Bridgman seal, sealingMechanism, radial expansion of plastically deformed seal material]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sealingMechanism
Context triple: [Bridgman seal, sealingMechanism, radial expansion of plastically deformed seal material]
  • A. sealingDefinition
    Indicates that one entity formally establishes or specifies the terms, conditions, or parameters under which a sealing or closure process is to occur.
  • B. sealType
    Indicates the specific kind or category of seal associated with an entity or connection.
  • C. sealedBy
    Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
  • D. mechanicalKeying
    Indicates that one entity physically engages or interlocks with another through a shaped mechanical interface (such as keys, slots, or profiles) to ensure correct positioning, alignment, or coupling.
  • E. usedSeal
    Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
  • 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_69c68a66554c8190add75c65942c0317 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f3b1f18881908140a6191d5478b5 completed March 27, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69c6f039f7248190bb4183f97b605763 completed March 27, 2026, 9:01 p.m.
PDg Predicate description generation batch_69c6f1ee5ab8819091082324f2dc3b8c completed March 27, 2026, 9:09 p.m.
Created at: March 27, 2026, 3:15 p.m.