Triple
T23244092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cepheid variables |
E581535
|
entity |
| Predicate | hasCauseOfPulsation |
P135594
|
FINISHED |
| Object | kappa mechanism |
—
|
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: kappa mechanism | Statement: [Cepheid variables, hasCauseOfPulsation, kappa mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCauseOfPulsation Context triple: [Cepheid variables, hasCauseOfPulsation, kappa mechanism]
-
A.
hasPulsations
Indicates that an entity exhibits rhythmic, repeated pulsating behavior or variations over time.
-
B.
pulsationMechanism
chosen
Indicates the physical process or mechanism responsible for producing and sustaining a periodic pulsation in an object or system.
-
C.
hasRadialPulsations
Indicates that an entity exhibits rhythmic expansions and contractions radiating outward from a central point.
-
D.
hasPulsationModes
Indicates that an entity exhibits specific modes or patterns of pulsation.
-
E.
hasNonRadialPulsations
Indicates that an entity exhibits pulsations or oscillations that are not purely radial, involving non-spherically symmetric modes of variation.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192efd44c8190b179b4d1cb71efa5 |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.