Triple

T17890017
Position Surface form Disambiguated ID Type / Status
Subject Fleming’s left-hand rule E447289 entity
Predicate helpsAvoid P17548 FINISHED
Object sign errors in direction of force 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: sign errors in direction of force | Statement: [Fleming’s left-hand rule, helpsAvoid, sign errors in direction of force]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: helpsAvoid
Context triple: [Fleming’s left-hand rule, helpsAvoid, sign errors in direction of force]
  • A. seeksToAvoid
    Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
  • B. designedToAvoid chosen
    Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
  • C. triedToAvoid
    Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
  • D. especiallyHelpsWhen
    Indicates that one entity is particularly beneficial or effective in assisting another entity or situation under certain conditions or circumstances.
  • E. oftenHelps
    Indicates that one entity frequently provides assistance or support to another.
  • 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_69d8b9f59bd48190a6fc925a855b8bac completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49d7828b481909b645fceb37a7ca3 completed April 19, 2026, 9:16 a.m.
PD Predicate disambiguation batch_69e3d8e9b77c8190bbfb508f28dfacfa completed April 18, 2026, 7:18 p.m.
Created at: April 10, 2026, 10:18 a.m.