Triple
T3487969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz force |
E73654
|
entity |
| Predicate | symbolForVelocity |
P48683
|
FINISHED |
| Object | v |
—
|
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: v | Statement: [Lorentz force, symbolForVelocity, v]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForVelocity Context triple: [Lorentz force, symbolForVelocity, v]
-
A.
symbolForLorentzFactor
Indicates that one entity is used as the symbolic representation of the Lorentz factor associated with another entity or context.
-
B.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
C.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
D.
hasTypicalVelocity
Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
-
E.
spinVariableSymbol
Indicates that a symbol represents the spin variable used in a physical or mathematical expression.
- 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_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb055ed2481908171effe28151cf9 |
completed | March 8, 2026, 5:22 p.m. |
Created at: March 8, 2026, 3:18 p.m.