Triple
T20542262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirac current |
E504368
|
entity |
| Predicate | appearsInInteractionTerm |
P118237
|
FINISHED |
| Object | e \bar{ψ} γ^μ ψ A_μ |
—
|
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 \bar{ψ} γ^μ ψ A_μ | Statement: [Dirac current, appearsInInteractionTerm, e \bar{ψ} γ^μ ψ A_μ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInInteractionTerm
Context triple: [Dirac current, appearsInInteractionTerm, e \bar{ψ} γ^μ ψ A_μ]
-
A.
appearsInContextWith
chosen
Indicates that two entities are observed or used together within the same situational, textual, or usage context.
-
B.
hasInteractionEffects
Indicates that one entity’s presence, action, or state alters, influences, or modifies the behavior, effect, or outcome associated with another entity.
-
C.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
D.
appliesToInteraction
Indicates that something (such as a rule, condition, or property) is relevant to or governs a specific interaction between entities.
-
E.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a292dd1c8190b5c3031f3b44eb52 |
completed | April 20, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.