Triple
T379995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooper pair |
E8656
|
entity |
| Predicate | existsBelow |
P12702
|
FINISHED |
| Object | critical temperature of superconductor |
—
|
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: critical temperature of superconductor | Statement: [Cooper pair, existsBelow, critical temperature of superconductor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsBelow Context triple: [Cooper pair, existsBelow, critical temperature of superconductor]
-
A.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
B.
clearanceBelow
Indicates that one entity is positioned at a lower vertical clearance level than another, typically with less space between it and an underlying reference surface.
-
C.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
- 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.