Triple
T26324602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slichter–Hebel coherence peak |
E662214
|
entity |
| Predicate | occursJustBelow |
P162328
|
FINISHED |
| Object | critical temperature Tc |
—
|
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 Tc | Statement: [Slichter–Hebel coherence peak, occursJustBelow, critical temperature Tc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursJustBelow Context triple: [Slichter–Hebel coherence peak, occursJustBelow, critical temperature Tc]
-
A.
occursBelow
Indicates that one event or object takes place or is positioned at a lower level or beneath another in a spatial or hierarchical sense.
-
B.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
C.
appearsBelow
Indicates that one entity is visually or spatially positioned lower than another in a layout, sequence, or display.
-
D.
mayBeBelow
Indicates that one entity is possibly, but not certainly, positioned lower than another in a spatial or ordered sense.
-
E.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6250321088190ae3ed1dc9f2fcd03 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f62473a38481909b919f88ffb5b492 |
completed | May 2, 2026, 4:21 p.m. |
Created at: April 26, 2026, 10:30 p.m.