Triple

T2091525
Position Surface form Disambiguated ID Type / Status
Subject Trouton–Noble experiment E32680 entity
Predicate aimedToDetect P23062 FINISHED
Object torque on a moving charged capacitor 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: torque on a moving charged capacitor | Statement: [Trouton–Noble experiment, aimedToDetect, torque on a moving charged capacitor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimedToDetect
Context triple: [Trouton–Noble experiment, aimedToDetect, torque on a moving charged capacitor]
  • A. detectorType
    Indicates the specific kind or category of detector associated with an entity or measurement.
  • B. requiresDetectionOf
    Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
  • C. aimsToMeasure chosen
    Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
  • D. aimedToImplement
    Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
  • E. aimsToSolve
    Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
  • 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_69a885eba0708190999696a45cbec816 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abba7626d081908c9c0f18942e128d completed March 7, 2026, 5:41 a.m.
PD Predicate disambiguation batch_69abb7b4356881909217c42ccb8bb1ed completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:43 p.m.