Triple

T19080539
Position Surface form Disambiguated ID Type / Status
Subject Karplus equation E467018 entity
Predicate hasMinimumCouplingNear P118122 FINISHED
Object 90 degrees dihedral angle 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: 90 degrees dihedral angle | Statement: [Karplus equation, hasMinimumCouplingNear, 90 degrees dihedral angle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMinimumCouplingNear
Context triple: [Karplus equation, hasMinimumCouplingNear, 90 degrees dihedral angle]
  • A. hasNearbyMode
    Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
  • B. isCloseTo
    Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
  • C. hasNearbyPoint chosen
    Indicates that one entity has at least one other point located within a specified proximity or distance from it.
  • D. hasNearbyFunction
    Indicates that one entity has another entity located close by that serves a related or supportive function.
  • E. hasMinimum
    Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
  • 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_69d8dd04f4488190b1121cc53ef2bfd6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e2e8f8148190942cca6dd3e30caf completed April 20, 2026, 8:25 a.m.
PD Predicate disambiguation batch_69e4b9a604308190a3235184f9f2c056 completed April 19, 2026, 11:16 a.m.
Created at: April 10, 2026, 12:04 p.m.