Triple
T8454340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirac notation |
E199881
|
entity |
| Predicate | symbolForState |
P82723
|
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, symbolForState, |ψ⟩]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForState Context triple: [Dirac notation, symbolForState, |ψ⟩]
-
A.
namedForStateRepresentation
Indicates that something is named in reference to a specific state’s political or governmental representation.
-
B.
symbolForConstant
Indicates that one entity serves as the symbolic representation or notation used to denote a particular constant.
-
C.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
D.
symbolRoot
Indicates a relationship where one symbol serves as the root or base form from which another symbol is derived or structured.
-
E.
symbolForSuccessor
Indicates that one entity serves as the symbolic representation or notation of the successor (the next element) of another entity in a sequence or structure.
- 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_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. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:10 p.m.