Triple
T26990746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rydberg molecule |
E679853
|
entity |
| Predicate | bondOrigin |
P161419
|
FINISHED |
| Object | shape resonance in electron-atom scattering |
—
|
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: shape resonance in electron-atom scattering | Statement: [Rydberg molecule, bondOrigin, shape resonance in electron-atom scattering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondOrigin Context triple: [Rydberg molecule, bondOrigin, shape resonance in electron-atom scattering]
-
A.
bondOrigin
chosen
Indicates the source or initiating entity, context, or event from which a particular bond or connection arises.
-
B.
agreementOrigin
Indicates that an agreement originates from, is derived from, or is based on a specified source or prior arrangement.
-
C.
bondChange
Indicates a change in the type, order, or presence of a bond between two entities, such as forming, breaking, or altering a connection.
-
D.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
E.
originatedInDenomination
Indicates that an entity began or was founded within a particular religious denomination.
- 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_69f6218fc6308190b1e3317de86703db |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:51 a.m.