Triple
T37418615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way bulge and bar |
E929784
|
entity |
| Predicate | hasResonance |
P149827
|
FINISHED |
| Object | corotation resonance in the inner disk |
—
|
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: corotation resonance in the inner disk | Statement: [Milky Way bulge and bar, hasResonance, corotation resonance in the inner disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResonance Context triple: [Milky Way bulge and bar, hasResonance, corotation resonance in the inner disk]
-
A.
isResonance
Indicates that one entity vibrates or responds in harmony with another, typically amplifying or reinforcing its effect or signal.
-
B.
isResonanceIn
chosen
Indicates that something functions as or exhibits a resonance within a specified medium, system, or context.
-
C.
isResonanceOf
Indicates that one entity is a resonance (e.g., an excited or alternative state) corresponding to another entity.
-
D.
resonanceWith
Indicates a relationship where one entity aligns, harmonizes, or meaningfully connects with another in a way that amplifies or reinforces its effect or significance.
-
E.
isResonantBecause
Indicates that one entity resonates or harmonizes with another specifically due to a stated cause or underlying reason.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.