Triple

T13185183
Position Surface form Disambiguated ID Type / Status
Subject Timet E313829 entity
Predicate hasKeyMaterialProperty P23698 FINISHED
Object high strength-to-weight ratio products 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: high strength-to-weight ratio products | Statement: [Timet, hasKeyMaterialProperty, high strength-to-weight ratio products]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKeyMaterialProperty
Context triple: [Timet, hasKeyMaterialProperty, high strength-to-weight ratio products]
  • A. hasKeyMaterial
    Indicates that an entity possesses or contains the cryptographic key material required for encryption, decryption, or related security operations.
  • B. hasMaterialType
    Indicates that something is composed of, made from, or characterized by a specific type of material.
  • C. hasKeyPolicy
    Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
  • D. hasKeyPass
    Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
  • E. haveProperty chosen
    Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
  • 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_69d806ae1e08819090d95bfe1538cc17 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98cf054f88190b05ced98d5a22a62 completed April 10, 2026, 11:51 p.m.
PD Predicate disambiguation batch_69d98bc6bc108190b5a6a265bf6e9fd4 completed April 10, 2026, 11:46 p.m.
Created at: April 9, 2026, 9:15 p.m.