Triple

T31171362
Position Surface form Disambiguated ID Type / Status
Subject Kimmie Meissner E794612 entity
Predicate technicalElement P86564 FINISHED
Object triple-triple jump combinations 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: triple-triple jump combinations | Statement: [Kimmie Meissner, technicalElement, triple-triple jump combinations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: technicalElement
Context triple: [Kimmie Meissner, technicalElement, triple-triple jump combinations]
  • A. technicalCrux
    Indicates a key technical challenge or bottleneck that critically determines the feasibility or success of a solution or system.
  • B. technicalType
    Indicates the specific technical category or classification that characterizes how something is implemented, structured, or functions.
  • C. technicalSpecialty
    Indicates that an entity has expertise or specialized knowledge in a particular technical field or domain.
  • D. isTechnical
    Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
  • E. hasTechnicalElement chosen
    Indicates that something includes, involves, or is characterized by a technical component, feature, or aspect.
  • F. None of above.

Provenance (3 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_69f224d5b9708190b6ca79ad2fd3a28a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69dfdda708190be290c7bec205445 completed May 3, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f69d1a37e081908d1d86b90ff502bd completed May 3, 2026, 12:55 a.m.
Created at: April 29, 2026, 9:07 p.m.