Triple

T27581947
Position Surface form Disambiguated ID Type / Status
Subject IBM Model F keyboard systems E699605 entity
Predicate mechanismComponent P162722 FINISHED
Object spring 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: spring | Statement: [IBM Model F keyboard systems, mechanismComponent, spring]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mechanismComponent
Context triple: [IBM Model F keyboard systems, mechanismComponent, spring]
  • A. mechanismBy
    Indicates that one entity occurs, is produced, or is brought about by means of another entity, which serves as its mechanism or causal process.
  • B. mechanismExample
    Indicates that one entity serves as an illustrative example of the mechanism or process by which another entity operates or produces an effect.
  • C. definesMechanism
    Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
  • D. mentionsMechanism
    Indicates that one entity explicitly refers to or describes the mechanism, process, or causal pathway by which another entity operates or produces an effect.
  • E. hasMechanism
    Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
  • 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_69ef6a4cb8b881909b3a8d630fd89df2 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63016cc1481908862c906df769a43 completed May 2, 2026, 5:10 p.m.
PD Predicate disambiguation batch_69f62c1921008190a62675a31f66a875 completed May 2, 2026, 4:53 p.m.
PDg Predicate description generation batch_69f62d14c24c81909e86678c1b5fd429 completed May 2, 2026, 4:57 p.m.
Created at: April 27, 2026, 2:03 p.m.