Triple
T26990744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rydberg molecule |
E679853
|
entity |
| Predicate | electronicState |
P181404
|
FINISHED |
| Object | highly excited Rydberg state |
—
|
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: highly excited Rydberg state | Statement: [Rydberg molecule, electronicState, highly excited Rydberg state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronicState Context triple: [Rydberg molecule, electronicState, highly excited Rydberg state]
-
A.
hasElectronicEffect
Indicates that one entity exerts or contributes an electronic influence or effect on another entity within a specified context.
-
B.
isElectronicOnly
Indicates that the item or resource exists solely in digital form and is not available in any physical format.
-
C.
powerStatus
Indicates whether an entity is currently powered on, off, or in another defined power state.
-
D.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
-
E.
usesElectricalPlug
Indicates that one entity operates by being connected to another entity via an electrical plug.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 27, 2026, 6:51 a.m.