Triple
T23006219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glauber coherent states |
E572775
|
entity |
| Predicate | nonOrthogonality |
P150616
|
FINISHED |
| Object | ⟨α|β⟩ ≠ 0 for α ≠ β |
—
|
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: ⟨α|β⟩ ≠ 0 for α ≠ β | Statement: [Glauber coherent states, nonOrthogonality, ⟨α|β⟩ ≠ 0 for α ≠ β]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonOrthogonality Context triple: [Glauber coherent states, nonOrthogonality, ⟨α|β⟩ ≠ 0 for α ≠ β]
-
A.
notAlignedWith
Indicates that one entity’s position, orientation, or viewpoint does not correspond or agree with that of another entity.
-
B.
notCrossing
Indicates that two entities do not intersect, overlap, or pass through each other in space or along their paths.
-
C.
nonperturbativeIn
Indicates that something occurs, is treated, or is valid in a nonperturbative regime or framework within a specified context or system.
-
D.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
E.
nonRepresentational
Indicates that the subject lacks representational content or does not depict or stand for anything beyond itself.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835706dc8190b3f9743c0f336bb2 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.