Triple

T1722351
Position Surface form Disambiguated ID Type / Status
Subject quantum electrodynamics E37418 entity
Predicate describesForce P31185 FINISHED
Object electromagnetic interaction 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: electromagnetic interaction | Statement: [quantum electrodynamics, describesForce, electromagnetic interaction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: describesForce
Context triple: [quantum electrodynamics, describesForce, electromagnetic interaction]
  • A. notableForce
    Indicates that an entity is recognized as a significant or influential force affecting another entity, system, or context.
  • B. primaryForce
    Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
  • C. besiegingForce
    Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
  • D. strategicPartnerForces
    Indicates a formal alliance in which one force provides coordinated military or security support to another as part of a shared strategic objective.
  • E. inForceIn
    Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
  • 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_69a8861acab88190bb43cde203429399 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aadb7bda1081908f2c41c520c9c55c completed March 6, 2026, 1:49 p.m.
PD Predicate disambiguation batch_69aa61c0a0288190bce9d60062a84b69 completed March 6, 2026, 5:10 a.m.
PDg Predicate description generation batch_69aadb68868c819097ec6db6194abae6 completed March 6, 2026, 1:49 p.m.
Created at: March 4, 2026, 7:30 p.m.