Triple
T379993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooper pair |
E8656
|
entity |
| Predicate | emergesFromInteraction |
P1257
|
FINISHED |
| Object | attractive electron–electron interaction |
—
|
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: attractive electron–electron interaction | Statement: [Cooper pair, emergesFromInteraction, attractive electron–electron interaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergesFromInteraction Context triple: [Cooper pair, emergesFromInteraction, attractive electron–electron interaction]
-
A.
emergedFrom
chosen
Indicates that one entity originated, arose, or came forth from another entity or source.
-
B.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
-
C.
emergedAround
Indicates that something came into existence or became noticeable at approximately a particular time or period.
-
D.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
E.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
- 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_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. |
Created at: Feb. 28, 2026, 1:08 p.m.