Triple
T8454342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirac notation |
E199881
|
entity |
| Predicate | symbolForInnerProduct |
P52975
|
FINISHED |
| Object | ⟨φ|ψ⟩ |
—
|
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: ⟨φ|ψ⟩ | Statement: [Dirac notation, symbolForInnerProduct, ⟨φ|ψ⟩]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForInnerProduct Context triple: [Dirac notation, symbolForInnerProduct, ⟨φ|ψ⟩]
-
A.
L2InnerProduct
chosen
Indicates that two entities are related by the standard Euclidean inner product, quantifying their similarity as the sum of pairwise products of their components.
-
B.
symbolForVelocity
Indicates that one entity is used as the symbolic representation or notation for the concept of velocity of another entity.
-
C.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
D.
hasSymbolicForm
Indicates that one entity serves as the symbolic representation or abstract form of another entity.
-
E.
symbolLinked
Indicates a relationship where one symbol is connected or associated with another symbol, typically to show reference, correspondence, or linkage between them.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48ca9988190b60ebd09a135194d |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.