Triple

T3487967
Position Surface form Disambiguated ID Type / Status
Subject Lorentz force E73654 entity
Predicate symbolForElectricField P49067 FINISHED
Object E 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: E | Statement: [Lorentz force, symbolForElectricField, E]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: symbolForElectricField
Context triple: [Lorentz force, symbolForElectricField, E]
  • A. associatedElectromagneticPotential
    Indicates that one entity stands in the role of the electromagnetic potential (e.g., scalar or vector potential) that is mathematically or physically associated with another entity.
  • B. magneticField
    Indicates the presence, strength, or configuration of a magnetic field associated with an entity or region.
  • C. magneticFieldStrength
    Indicates the intensity or magnitude of a magnetic field associated with an entity or at a specific location.
  • D. electricalConductivity
    Indicates that one entity has the ability to conduct electric current through it, typically quantified as a measure of how easily charge flows within that material or medium.
  • E. symbolForLorentzFactor
    Indicates that one entity is used as the symbolic representation of the Lorentz factor associated with another entity or context.
  • F. None of above. chosen

Provenance (4 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_69ad85cca8d4819088494e9f3340fab5 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbb9193688190aa0cbf87a7b99446 completed March 8, 2026, 6:10 p.m.
PD Predicate disambiguation batch_69adae0935ac8190bfa8a8bd3dcd3301 completed March 8, 2026, 5:12 p.m.
PDg Predicate description generation batch_69adb1ecb02881908394f197e31431b4 completed March 8, 2026, 5:29 p.m.
Created at: March 8, 2026, 3:18 p.m.