Triple
T26990725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rydberg molecule |
E679853
|
entity |
| Predicate | typicalBindingEnergy |
P1457
|
FINISHED |
| Object | MHz scale |
—
|
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: MHz scale | Statement: [Rydberg molecule, typicalBindingEnergy, MHz scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBindingEnergy Context triple: [Rydberg molecule, typicalBindingEnergy, MHz scale]
-
A.
bindingEnergyRelativeToHydrogen
Indicates the amount of binding energy an entity has, expressed relative to that of hydrogen as a reference.
-
B.
hasBindingEnergy
Indicates that one entity possesses or is characterized by a specific amount of binding energy associated with its formation or stability.
-
C.
typicalBonding
Indicates a usual or characteristic bonding relationship that commonly occurs between the involved entities.
-
D.
bindingTypical
Indicates that one entity commonly or characteristically binds to another under typical or standard conditions.
-
E.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: April 27, 2026, 6:51 a.m.