Triple
T379981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooper pair |
E8656
|
entity |
| Predicate | hasTypicalSpinState |
P12700
|
FINISHED |
| Object | spin singlet |
—
|
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: spin singlet | Statement: [Cooper pair, hasTypicalSpinState, spin singlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSpinState Context triple: [Cooper pair, hasTypicalSpinState, spin singlet]
-
A.
hasSpin
Indicates that one entity possesses or exhibits rotational motion or angular momentum.
-
B.
hasGroundState
Indicates that an entity possesses a lowest-energy, most stable state in its energy configuration.
-
C.
hasIsospin
Indicates that one particle possesses a specific isospin value or quantum number in relation to another reference or classification framework.
-
D.
hasTotalAngularMomentumJ
Indicates that an entity possesses a specified value of total angular momentum quantum number J.
-
E.
hasTypicalBeam
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2eae0bd7081908197bbf5c55fe647 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.